Framework → Implementation Status
PartialStatus of each canonical step in the current codebase.
Status
| Step | Name | Status | Note |
|---|---|---|---|
| 1 | Upload | implemented | User uploads IFC/STEP → stored in R2 → metadata in Postgres. |
| 2 | Contextual Enrichment | partial | The master brief stores validated structured context in Postgres. The live chat path streams OpenAI tokens and does not persist a structured context record as a first-class entity. |
| 3 | Structural Processing | implemented | Worker parses file → builds graph → stores in Neo4j. |
| 4 | Reference Preparation | mock | pgvector and a live document ingest pipeline are target architecture. Current preparation loads synthetic seed JSON into process memory. |
| 5 | Decision Setup | implemented | User configures agent architecture in canvas → stored in Postgres. |
| 6 | Planner Execution | implemented | Planner loads structural graph, reference memory, canvas config, and user context. |
| 7 | GraphRAG Retrieval | partial | Retrieval is MD5 lexical hashing over synthetic seeds, not pgvector. GNN signals are not present. |
| 8 | Agent Interaction | partial | Agents exchange structured messages → user may intervene. |
| 9 | Decision Output | implemented | Results stored in Decision Memory → dashboard generated. |
| 10 | FRAMEWORK DEFINITION REQUIRED | designed | Do not treat Evaluation Hooks as the official Step 10 name. The canonical brief stops at Step 9. A named Step 10 requires an architecture / research clarification. |