core-labs/core
core-labs/core
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity
core/docs
History
Shay dccce6a7b9 fix(generate): a proposition graph must be able to represent denial (ADR-0265) 
CORE served the affirmative of propositions the user denied. Measured live on
main @ 536d6e55 with realizer_grounded_authority=True:

    "evidence does not support truth" -> 'Evidence is verified: what supports truth.'
    "evidence supports truth"         -> 'Evidence is verified: what supports truth.'

Byte-identical.

Phase 4 (#136) pinned "render_semantic has no negated parameter" as a defect.
Sizing the exposure before acting on it -- the step §7 requires -- showed the
pin was correct and INCOMPLETE. The defect is two drops in series, and the
first is in the graph:

  intent.negated      parsed from the user's words, always has been
  GraphNode           NO FIELD FOR IT  <-- first drop
  ground_graph        rebuilds nodes field-by-field; nothing to carry
  depth enrichment    rebuilds nodes field-by-field; nothing to carry
  plan_articulation   cannot carry what the node does not hold
  realize_semantic    never read step.negated
  render_semantic     no parameter for it                <-- second drop

Five separate constructors, each silently defaulting to the affirmative.

Why every gate was green
------------------------
On the default config the ungrounded realizer emits "...", _is_useful_surface
rejects it, and the runtime echo wins the resolver -- and the echo contains the
user's own "does not". The truth path was correct BY ACCIDENT. ADR-0088 Phase B
grounds the graph first, which is exactly when the realizer's surface becomes
useful enough to win. So the defect sat behind a shipped flag, invisible to
every property-of-one-surface test, because nothing compared a denial to its
assertion.

Delivered
---------
- GraphNode.negated, threaded intent -> graph -> ground -> enrich -> step ->
  surface. Serialized ONLY when True, so every pre-existing as_dict and every
  trace_hash folded from one stays byte-identical -- which is why no lane pin
  moves.
- Clause grammar delegated to its one owner. Four of the eight intent
  "templates" were never frames; they were plain clauses. They now call
  render_step. Writing a second negation implementation in semantic_templates
  was the tempting fix and is rejected: Phase 2A spent a unit giving every
  linguistic fact one owner, and that design rebuilds the disease one level up.
- Frames that keep a finite verb (VERIFICATION, PROCEDURE, COMPARISON) get an
  explicit negated form. RECALL is a speech act with no proposition to deny, so
  it falls back to the clause path rather than drop the denial (ADR-0261 §5.1).

Measured
--------
    delegation on affirmatives          192/192 byte-identical
    serving realizer, all corpora       85/347 -> 109/347   (+24 = the denials)
    feature-bearing bucket              49/214 -> 73/214
    CONTROL (nothing droppable)         33/33  -> 33/33     unchanged
    multi-node (clause joining)         3/100  -> 3/100     unchanged, out of scope
    lane pins                           11/11 byte-identical, none edited

The control staying 33/33 and multi-node staying 3/100 is the evidence that
this moved the denials and nothing else.

The exhaustive control earned its keep immediately
--------------------------------------------------
It found FIVE more intents serving a denial as its own assertion --
TRANSITIVE_QUERY, FRAME_TRANSFER, NARRATIVE, EXAMPLE, DEDUCTION -- because an
intent with no frame fell back to the UNKNOWN *template* (which cannot say
"not") rather than the UNKNOWN *clause* (which can). The default is now the
capable path, so the next intent added inherits correctness. Found by the
control, not by inspection.

Mutation -- every link reverted individually
--------------------------------------------
    baseline                                        19 pass
    graph_from_intent drops intent.negated           8 FAIL
    plan_articulation drops node.negated             6 FAIL
    ground_graph drops it on rebuild                 2 FAIL
    realize_semantic stops passing step.negated      6 FAIL
    unframed intents fall back to the template       1 FAIL
    pipeline depth-enrichment drops it               1 FAIL

The last row was GREEN on the first run -- my fix there was unguarded. That is
what added the structural invariant: every GraphNode(...) built on the serving
path must NAME `negated` or be recorded in an allowlist with a reason. The
defect was five constructors; a per-site test must be written per site, and a
site added without one is invisible. Only recognition/connector.py is exempt
(an EpistemicNode has no polarity to carry).

Four Phase 4 pins are revised, not relaxed -- #136's M2 mutation ("render_semantic
GAINS a negated parameter -> FAIL") has now happened for real, and forced the
deliberate revision it was built to force.

Registered in `smoke` in the same PR that creates it, per the #136 finding that
an unregistered pin runs nowhere.

Still unexpressed, deliberately: quantifier, tense, aspect. NO PRODUCER sets
them anywhere on the serving path, so threading them would be machinery with no
caller. render_step already handles all three the moment a producer exists.

[Verification]: in-worktree on CPython 3.12.13 with `uv sync --locked` --
smoke 641 (was 621), deductive 503, lane pins 11/11 with no pin edited.
2026-07-27 13:08:17 -07:00
..
adr fix(generate): a proposition graph must be able to represent denial (ADR-0265) 2026-07-27 13:08:17 -07:00
agents/grok
analysis feat(coherence): grounded-open hedge arm — serve pack surfaces honestly hedged instead of over-refusing (ADR-0254) 2026-07-23 01:27:17 -07:00
architecture
audit docs: accept ADR-0246, 0247, 0248 and update packet 2026-07-18 11:18:51 -07:00
benchmarks
briefs docs(governance): weekly-audit rulings T1/T7/T8/T9 — INV-32/33/34 registration, ADR-0243 fold, residual escalation, path sweep, prune ledger 2026-07-22 19:18:59 -07:00
curriculum Lane 4: Registry Consolidation (language_packs to packs) 2026-07-04 15:11:28 -07:00
decisions
evals chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
examples
handoff docs(arc): reconcile the arc's records with what the units measured 2026-07-26 12:33:30 -07:00
handoffs docs(paradigm): retire six competing unratified problem-solving paradigms under ADR-0252 2026-07-19 14:46:47 -07:00
implementation docs(paradigm): retire six competing unratified problem-solving paradigms under ADR-0252 2026-07-19 14:46:47 -07:00
issues fix(tests): session-scoped engine-state isolation baseline — close module-scope escape to the live life-store 2026-07-22 20:32:06 -07:00
lab
outreach
paradigm-archive docs(paradigm): retire six competing unratified problem-solving paradigms under ADR-0252 2026-07-19 14:46:47 -07:00
plans fix(generate): a proposition graph must be able to represent denial (ADR-0265) 2026-07-27 13:08:17 -07:00
research Merge pull request 'Rust parity: cargo green, lane parity unfalsifiable — plus core rust build was broken (plan §6A)' (#124) from fix/rust-build-env-and-parity-report into main 2026-07-26 20:20:16 +00:00
sessions
specs fix(runtime): defer the turn-event sink emission to the serve boundary (R7) 2026-07-26 10:56:03 -07:00
workbench docs(governance): weekly-audit rulings T1/T7/T8/T9 — INV-32/33/34 registration, ADR-0243 fold, residual escalation, path sweep, prune ledger 2026-07-22 19:18:59 -07:00
zig chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
3lang-depth-pr-plan.md
admissibility-exemplars.md
ci-optimization.md ci: fast-lane main gate, nightly full suite, skip-safe lane-shas 2026-07-14 21:02:43 -07:00
core-rd-base-prompts.md
ethics_packs.md chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
EVAL_AUDIT_2026-05-20.md
eval_methodology.md
frontier_baselines.md
gaps.md
handoff_template.md
hitl-backpressure.md
holdout_recipients.txt
identity_packs.md chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
master-plan-post-substrate-audit.md
memo.html
model_dependency_size_tally.md
pack_inventory_2026-05-21.md
position_paper.md
PROGRESS.md
README.md
recognizer-registry.md
refusal-taxonomy.md
reviewers.yaml
RUST.md fix(algebra): P11a physics hot paths via algebra.backend (Rust-ready) 2026-07-14 21:08:02 -07:00
safety_packs.md chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
sponsors.md docs: remove unestablished NSF SBIR and DARPA claims from Path B 2026-06-25 14:36:12 -07:00
teaching_order.md chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
test-debt-quarantine.md
testing-lanes.md feat: close ADR-0241/0242 post-Accept backlog (local-first mastery) 2026-07-16 15:25:43 -07:00
Whitepaper.md chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
Yellowpaper.md Lane 4: Registry Consolidation (language_packs to packs) 2026-07-04 15:11:28 -07:00

README.md

CORE Documentation Index

This is the central index for all documentation in the CORE project.

Canonical Root Documents

Directories

Architecture & Design

  • adr/ - Architecture Decision Records (ADRs). The canonical history of all ratified engineering choices.
  • architecture/ - High-level architectural documents (e.g., pipelines, schemas).
  • analysis/ - Deep dives and master plans for structural changes.
  • specs/ - Detailed technical specifications and invariants.

Planning & Progress

  • plans/ - Capability roadmaps and implementation plans.
  • briefs/ - Project briefs and scoping documents for upcoming work.
  • issues/ - Detailed issue analyses and technical reproductions (not standard trackers).
  • audit/ - Audit reports and claims ledgers.

Operations & Usage

  • examples/ - Usage examples and reference integrations.
  • workbench/ - Documentation for the CORE workbench UI and related tooling.
  • agents/ - Agent-specific operational guides.

    Note regarding agents/grok/: Operational guide for using Grok 4.3 + Grok Build with CORE. This is not architecture documentation.

Learning & Evaluation

  • curriculum/ - Documentation on the teaching/learning order and knowledge progression.
  • evals/ - Evaluation methodology and performance criteria documentation.
  • benchmarks/ - Benchmark evidence and performance tracking logs.

Historical & Experimental

  • sessions/ - Chronological session logs documenting the "decision trail" and intellectual history of major choices.
  • handoffs/ - Legacy brief, audit, and investigation notes (historical; the formal HANDOFF mechanism is retired — see AGENTS.md for the current lightweight session-break-summary-<DATETIME>.md convention).
  • research/ - Raw research notes and preliminary findings.
  • lab/ - Experimental content (Warning: Not ratified; must not be referenced as authoritative in production PRs).

External

  • outreach/ - External communications and messaging.
  • zig/ - Scoped documentation for the Zig language components.