T-1.1
Request → Materialize
Not yet tested
Hypothesis: A file can be generated on demand from graph state alone, without any prior file existing on disk.
Test: Delete
src/config/config.ts from disk (keep graph intact). Request "give me config.ts". System queries graph for config-related entities and assembles projection with correct imports, type definitions, export structure, and formatting.
Pass: Generated file compiles. TypeScript type-checks. Exported interface matches what dependents expect.
Fail: Generated file does not compile, or loses critical information that was only encoded in file structure.
T-1.2
Materialize → Edit → Reconcile
Not yet tested
Hypothesis: Edits to a materialized file can be parsed back into graph mutations.
Test: Materialize a projection. Make 3 edits: add a new function, change a parameter type, remove an import. Reconcile: parse diff into graph operations. Apply operations. Re-materialize projection.
Pass: Re-materialized file contains all 3 edits. Graph contains new entity. Removed import reflected as deleted edge.
Fail: Any edit is lost, misinterpreted, or causes graph inconsistency.
T-1.3
Dissolve
Not yet tested
Hypothesis: After reconciliation, the file on disk can be deleted without information loss. The graph is sufficient.
Test: Start with fully reconciled graph state. Delete all
.ts files from src/. Re-materialize entire project from graph. Run npm run build.
Pass: Build succeeds. All tests pass. No information was stored only in files.
Fail: Build fails due to information that existed only in file-level artifacts.