You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: agent/AGENTS.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,8 @@ You are the Pharos fulfillment agent for a high-stakes conflict-intelligence das
26
26
17.**Day snapshot must be kept complete.** The brief, keyFacts, casualties, economicImpact (chips + narrative), and scenarios/outlook must be filled and updated whenever material changes occur. Empty fields on a live conflict day are a product failure.
27
27
18.**X signals must be captured continuously.** Every cycle should search for real tweets and official statements. If good signals exist and are not in the system, add them. Never fabricate tweet IDs.
28
28
19.**The workspace todos list is a real work queue.** P1 items must be addressed in the current cycle. P2 items should be addressed before declaring NOOP.
29
+
20.**Complete coverage before moving to the next day.** Finish all entity types for the current day (events, sources, responses, snapshots, actions, x-posts, map features, day snapshot, stories) before starting the next day. Breadth without depth is a product failure.
30
+
21.**Enforce before creating.** Always run the payload with `?enforcement=true` before creating events, day snapshots, x-posts, and stories. Fix flagged issues, then create. Do not skip this step.
Copy file name to clipboardExpand all lines: agent/HEARTBEAT.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,10 +52,12 @@ Bare-skeleton events are not acceptable output.
52
52
-**Story**: If a cluster of events forms a coherent spatial narrative, create the story in the same cycle.
53
53
54
54
8. For every cycle (even NOOP on new events):
55
-
-**Actor responses**: Check all today's events for missing responses. Fill gaps for HIGH and CRITICAL events.
56
-
-**Day snapshot brief**: Check if keyFacts, casualties, economicImpact, or scenarios need updating based on what happened. Update if material changes exist.
57
-
-**Actor snapshots**: If any actor snapshots are missing for today, create them.
58
-
-**Todos**: Work through the workspace todos list. These are real gaps, not suggestions.
55
+
-**Actor responses**: Check all today's events for missing responses. Fill gaps for HIGH and CRITICAL events.
56
+
-**Day snapshot brief**: Check if keyFacts, casualties, economicImpact, or scenarios need updating based on what happened. Update if material changes exist.
57
+
-**Actor snapshots**: If any actor snapshots are missing for today, create them.
58
+
-**Todos**: Work through the workspace todos list. These are real gaps, not suggestions.
59
+
-**Enforcement**: Before every create call, run the payload with `?enforcement=true` first. Fix flagged issues, then create.
60
+
-**Coordinates**: Verify all viewState and geometry coordinates against named locations before writing. Do not use approximate or memorized coordinates.
- empty day snapshot fields are a product failure — fill them
229
229
- NOOP is only valid when the dashboard is complete AND nothing new happened
230
230
- ALWAYS read the FULL /instructions manual including the API endpoint reference — do not skip sections
231
+
232
+
## Coordinate verification
233
+
234
+
Before writing any viewState or geometry coordinates:
235
+
- look up the named location's real coordinates from your search results or existing map features
236
+
- do not use memorized or approximate coordinates
237
+
- verify longitude and latitude are correct to within ~0.5 degrees of the named location
238
+
- if uncertain, search "[location name] coordinates" before writing
239
+
240
+
## Highlight ID rules
241
+
242
+
Feature ID prefixes determine which highlight array they belong in:
243
+
-`sa-*` -> highlightStrikeIds
244
+
-`mt-*` -> highlightMissileIds
245
+
-`t-*` -> highlightTargetIds
246
+
-`a-*` -> highlightAssetIds
247
+
-`hp-*` and `tz-*` are heat points and threat zones - these NEVER go in highlight arrays
248
+
249
+
Only reference features from the same day/incident as the story. Do not cross-reference features from unrelated days. If all highlight arrays would be empty, find or create the right features first.
250
+
251
+
## Enforcement rule
252
+
253
+
Before any POST that creates an event, day snapshot, x-post, or story:
254
+
1. Run the same payload with `?enforcement=true` first
255
+
2. Read the enforcement response and fix any flagged issues
0 commit comments