Structs Reconnaissance

Procedure

1. Query entities — All via structsd query structs [subcommand] [args]:
   • Players: player [id], player-all
   • Planets: planet [id], planet-all, planet-all-by-player [player-id], planet-attribute [planet-id] [type], planet-attribute-all
   • Structs: struct [id], struct-all, struct-attribute [id] [type], struct-type [id], struct-type-all
   • Fleets: fleet [id], fleet-all, fleet-by-index [index]
   • Guilds: guild [id], guild-all, guild-membership-application [id], guild-membership-application-all
   • Energy: reactor [id], reactor-all, infusion [id], infusion-all, infusion-all-by-destination [dest-id], provider [id], provider-all, agreement [id], agreement-all, agreement-all-by-provider [provider-id]
   • Power: allocation [id], allocation-all, allocation-all-by-source [source-id], allocation-all-by-destination [dest-id], substation [id], substation-all
   • Grid: grid [id], grid-all
   • Block: block-height
2. Assess targets — For players: structs, power capacity, fleet status (onStation = can build; away = raiding). For planets: ore remaining, defense structs, shield. For guilds: members, Central Bank status.
3. Identify vulnerabilities — Unrefined ore stockpile, power near capacity, undefended planet, fleet away (raiding).
4. Persist intelligence — After gathering, update:
   • memory/intel/players/{player-id}.md — Player dossier (profile, behavior, vulnerabilities, relationship)
   • memory/intel/guilds/{guild-id}.md — Guild profile (members, bank status, strengths, weaknesses)
   • memory/intel/territory.md — Planet ownership, ore, defense levels
   • memory/intel/threats.md — Threat board ranked by severity

Commands Reference

Verification

• Re-query entity after action to confirm state change.
• Cross-reference: player → planet → struct → fleet for full picture.
• Block height confirms chain sync.

Error Handling

• Entity not found: ID may be invalid or entity destroyed. Try -all variants to discover current IDs.
• Stale data: Query block-height; re-run queries if chain has progressed.
• Missing intel files: Create memory/intel/players/, memory/intel/guilds/ if absent. Follow formats in memory/intel/README.md.

Intelligence Persistence Loop

1. Run reconnaissance queries for target(s).
2. Parse results: owner, structs, power, shield, fleet status, guild.
3. Write/update memory/intel/players/{player-id}.md, memory/intel/guilds/{guild-id}.md per memory/intel/README.md formats.
4. Update memory/intel/territory.md with planet ownership table.
5. Update memory/intel/threats.md with ranked threats and response notes.
6. Include “Last Updated” date in each file.

See Also

• memory/intel/README.md — Dossier formats, territory map, threat board
• awareness/threat-detection.md — Using intel for threats
• awareness/opportunity-identification.md — Spotting opportunities
• knowledge/mechanics/combat.md — Raid mechanics, fleet status
• playbooks/meta/reading-opponents.md — Soul type identification