SYS.30 / INTELLIGENCE
Project Intelligence
The structured understanding [the Constitution](/docs/constitution) and every [Skill](/docs/skills) are written from. Not prose — a typed object, every field of which carries a confidence.
What it holds
Four kinds of statement about one project.
- What this is
- The product or system the repository implements, in the terms the repository itself uses — read from documentation, public routes and naming, not guessed from the dependency list.
- What it is built from
- Languages, frameworks, versions and configuration, each traceable to the manifest or parse tree that established it.
- How it is arranged
- Module boundaries, the dependency shape, where the weight sits, and which files are load-bearing.
- What could not be established
- Explicitly. This is the field most comparable tools do not have.
How it is built
Selection, then specialised passes, then a merge.
- SELECTIONPARSED
Rank and chunk the files worth reasoning about. Manifests, schemas, route files and heavily imported modules score high; tests and generated output score low.
- ANALYSIS PASSESREASONED
Specialised passes over chunk groups, in parallel with a capped concurrency. Each returns structured output against a schema, never prose to be parsed.
- SYNTHESISREASONED
One merge of everything prior into the intelligence object.
- THE GATEGATE
Citations re-validated against the file index; unsupported claims demoted before anything is stored.