core-labs/core
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions
core/docs/sessions/2026-05-13.md
Shay 310aed9ff0
chore: Refactor CLI and Governance Anchors (#926) 
* docs: consolidate governance anchors and clean up test registries

* refactor(cli): decompose cli into dedicated modules

* test: fix broken test baselines and formatting

* docs: add domain boundary READMEs for governance anchors

* test: update baseline for determination lane

* test: fix capability_pass expectation

* test: fix CORE_SHOWCASE_SKIP_BUDGET enforcement

* chore: cleanup CLI extraction and unreachable code
2026-07-03 12:34:56 -07:00

2.4 KiB
Raw Permalink Blame History

Session Note — 2026-05-13

Key Clarification: core is the primary work. core-ai is the archive.

Context

AssetOverflow/core-ai was the original implementation of the Versor Engine. Over time it drifted from its architectural intent — the geometry got buried under operational infrastructure: CoreChatRuntime, RuntimeMemoryAuthority, GradeGuard, core_logos as a full articulation subsystem, core_ca as an apprenticeship platform, bounded continuity state, proof scripts, and a deployed-product authority hierarchy (core_ha, core_vault, core_logos, core_engine as separate governance domains).

That work was real engineering but it was solving the wrong problem at the wrong time — it was building a product on top of the model before the model itself was defined and correct.

AssetOverflow/core is the reset: back to first principles, two primitives, one injection gate, the field as native state, Cl(4,1) as the only substrate. Every layer has exactly one job.

Decision

  • AssetOverflow/core is the primary, active, authoritative repository.
  • AssetOverflow/core-ai is a reference archive. It is not a source of patterns, conventions, or designs to pull forward unless they are explicitly evaluated against the seven axioms and the three engineering pillars in core's README.
  • The following from core-ai are worth reviewing for future mining (not direct import):
    • core_ingest — CandidateGeometricPressure design and governance tier
    • core_vault — frozen storage semantics
  • The following from core-ai must not be re-introduced into core:
    • Any chat runtime, authority hierarchy, or proof-script infrastructure
    • core_logos as a subsystem (articulation in core is a thin final layer, not a subsystem)
    • core_ca apprenticeship layer (out of scope for the engine itself)
    • RuntimeMemoryAuthority or any tiered memory governance (vault + field are sufficient)

Structural Issues Fixed This Session

  • pyproject.toml: renamed package from core-ai to core-versor
  • core/__init__.py: created — the core/ Python package previously had no top-level init
  • ADR-0011 written: Renderer layer contract

Open Items

  • ingest/gate.py is the correct shape but core_ingest's CandidateGeometricPressure envelope design deserves evaluation as a pre-gate normalization step (see previous session analysis)
  • docs/adr/README.md ADR index needs update through ADR-0011