Constellation

Project context lives across tickets, wikis, and repositories without a reliable connection map.

Project knowledge usually lives scattered across ticketing, wiki, and source control with no automatic map of how it connects.

The first figure follows a seed through crawl, tiering, review, and hub preview. The second is the safety model that keeps every implemented command read-only.

I built Constellation to start from a single seed and crawl outward through connectors that share one contract, scoring each link by weighted distance and corroboration into a Tier 1-4 graph. The result is a schema-validated connections manifest (nodes, edges, evidence, and human decisions to confirm, reject, or mute a candidate). A renderer turns that into a multi-page hub preview and a publish plan, entirely offline from a write perspective.

GET-only HTTP is enforced in the session layer and asserted by tests; creating or updating real wiki pages is a separately gated final milestone.

Connector contract

Ticketing and wiki connectors implement one shared node/edge/evidence interface so a new source system is an adapter, not a special case.

Identity merge

The same person found in two systems collapses to one node via a stable account-keyed identity.

Evidence first

Every claim carries a locator and fetch time; freshness and uncertainty are explicit fields, not implied.

Write deferral

Updating real wiki pages is reserved for a final, separately approved milestone against allowlisted managed regions.

BRIEF.md is the handoff format that feeds the same graph-shaped memory. Orchestration engineering is the spawn-engine sibling; compress for agents is why the handoff stays small.