core-labs/core
core-labs/core
1
0
Fork 0
Code Issues Pull requests 2 Projects Releases Packages Wiki Activity
core/docs/sessions/2026-05-13.md
Shay 54e6bfc0d0
docs: reorganize docs landscape 
Implements the 4-phase documentation reorganization master plan.

- Consolidation: Merged brief/, handoff/, planning/, and decisions/ into briefs/, handoffs/, plans/, and adr/ respectively (101 ADRs relocated)
- Root Cleanup: Relocated HANDOFF-gpt55-*.md and key top-level docs (runtime_contracts.md, etc.) to canonical folders. Added superseded alerts.
- Indices & Navigation: Created docs/README.md navigation document, docs/sessions/README.md index, docs/adr/README.md index
- Note: Also includes prior commit adding ADR-0200+ corpus hygiene governance (ADR-0225, dependency map, backfilled cross-references)
2026-06-30 16:59:36 -07:00

2.4 KiB
Raw 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/decisions/README.md ADR index needs update through ADR-0011