Revision history

The book stays intact. The examination history stays visible.

This is the rendered companion record for Building Specialty Packs. The First Edition is not silently rewritten. New pressure tests, corrections, external reviews, and examination-backed refinements are added here with provenance, evidence status, and bounded claim language.

How to read the record
Origin

Who introduced the pressure test, distinction, or falsifier.

Evidence status

What was actually examined, accepted, pending, or merely proposed.

Claim ceiling

Where the evidence stops so later readers do not inherit a stronger claim.

R-001–R-010
Semantic continuity
R-011–R-018
Authority, evidence & consequence identity
R-019–R-025
Examination-backed authority boundaries
R-026–R-030
External review refinements
R-031–R-035
Artifact & evidence method
R-001 → R-010

Semantic continuity

How apparently stable values can hide changed scope, meaning, source, evidence, time semantics, or consequence identity.

R-001

Proposition continuity is not value continuity

Origin: J Harlow adversarial sequence; refinement accepted by Tim.

ACCEPTED FOR REVISION.

Unified invariant:

A governed proposition is continuous only to the extent that the Pack can establish continuity of the material semantic dimensions under which that proposition was constituted. Value continuity alone is insufficient. No Pack may infer continuity where any material semantic dimension is missing, unrepresented, stale, or semantically drifted.

Material semantic dimensions (declarative, not mechanically mandatory):

  • value lineage
  • scope lineage
  • applicability/surface lineage
  • interpretive-rule lineage
  • source lineage
  • evidence-set lineage
  • temporal-semantics lineage
  • effect-identity lineage
  • cross-predicate coupling lineage

Revision principle: Each Specialty Pack declares which semantic dimensions are material for each governed proposition, preserves attributable lineage for those dimensions, and refuses assumed continuity when a material dimension is unresolved or drifted.

R-002

Payments: destination-transition lineage

Origin: J Harlow adversarial Payments case.

ACCEPTED FOR REVISION.

Problem: A stable destination_verified=true can conceal a material destination substitution if verification scope is too coarse.

Required facts:

  • effect_instance_id
  • prior_destination
  • current_destination
  • destination_changed
  • verification_scope
  • prior_effect_execution_state = NOT_ATTEMPTED | REJECTED | ACCEPTED | AMBIGUOUS
  • ordered destination/effect history when more than one transition exists

Rule: Ambiguous provider acceptance + destination change must never be representable as continuity.

R-003

Payments: authority-scope lineage

Origin: J Harlow authority-scope falsifier.

ACCEPTED FOR REVISION.

Problem: Favorable booleans such as amount_within_grant=true or payment_delegated=true can remain unchanged while the scope under which they were established materially narrows.

Required facts:

  • prior_approval_scope
  • current_approval_scope
  • prior_delegation_scope
  • current_delegation_scope
  • source/version/effective-time metadata
  • scope lineage tied to the effect instance

Derived change flags: Only under explicit, versioned comparison rules.

Invariant: Authority continuity cannot be inferred from proposition continuity.

R-004

Payments: restriction-surface lineage

Origin: J Harlow third falsifier.

ACCEPTED FOR REVISION.

Problem: restriction_active=false can remain stable while the registry's applicability surface changes (jurisdiction, vendor class, risk class, or applicability domain).

Required facts:

  • prior/current restriction surface
  • restriction surface source
  • effective time
  • surface lineage tied to effect instance
  • versioned comparison rule for any restriction_surface_changed field

Invariant: Restriction-state continuity cannot be inferred from restriction-value continuity.

R-005

Interpretive-rule lineage

Origin: J Harlow fourth falsifier; independently reinforced by Christoph Svoboda.

ACCEPTED FOR REVISION.

Problem: Same value + same scope can still mean something different after the evidence-to-proposition rule changes.

Required facts:

  • prior/current rule version
  • rule source
  • effective time
  • rule lineage tied to proposition/effect
R-006

Source lineage

Origin: J Harlow fifth falsifier.

ACCEPTED FOR REVISION.

Problem: Same value, scope, and rule can be produced by a materially different source (primary, fallback, mirror, cache, degraded source).

Required facts:

  • prior/current source identity
  • source type
  • source effective time
  • source lineage
  • declared competence/coverage characteristics where material
R-007

Evidence-set lineage

Origin: J Harlow sixth falsifier.

ACCEPTED FOR REVISION.

Problem: Same value, scope, rule, and source can be produced from a materially different evidence set.

Required facts:

  • prior/current evidence set or stable evidence-set reference
  • evidence-set source
  • effective time
  • lineage tied to proposition/effect
R-008

Effect-identity lineage

Origin: J Harlow seventh falsifier.

ACCEPTED FOR REVISION.

Problem: A stable effect_instance_id string does not guarantee the same governed effect after clone, replay, merge, fork, or reconstruction.

Required facts where material:

  • effect lineage ID
  • parent/child relationships
  • creation source
  • replay count
  • merge/fork metadata
  • reconstitution source
  • lineage version
  • consequence-chain binding

Invariant: Effect-lineage continuity cannot be inferred from identifier continuity.

R-009

Temporal-semantics lineage

Origin: J Harlow eighth falsifier.

ACCEPTED FOR REVISION.

Problem: A timestamp can remain lexically fresh while timebase, freshness window, validity horizon, or clock semantics change.

Required facts where material:

  • prior/current temporal semantics
  • timebase
  • freshness window
  • validity horizon
  • clock drift / synchronization basis
  • effective time and lineage

Invariant: Temporal continuity cannot be inferred from timestamp continuity.

R-010

Cross-predicate coupling lineage

Origin: J Harlow ninth falsifier.

ACCEPTED FOR REVISION.

Problem: Every predicate can remain individually continuous while the institution changes the joint semantics among them.

Examples:

  • authority becomes conditional on destination jurisdiction
  • restriction applicability becomes conditional on delegation scope
  • verification scope becomes conditional on invoice class

Required facts where material:

  • prior/current joint semantics
  • joint-semantics source
  • effective time
  • lineage

Invariant: Individual predicate continuity does not imply joint semantic continuity.

R-011 → R-018

Authority, evidence & consequence identity

Source standing, fixation, evidence admission, recursive authority, and the boundaries that keep constitution attributable.

R-011

Source continuity is not source standing

Origin: Wojciech Z. Kaleta post-V116 proposed examination.

ACCEPTED FOR REVISION / EXAMINATION TO BE FROZEN.

Problem: A source can remain fresh, attributable, available, unchanged, and historically primary while losing current governing authority for the proposition.

Source-responsibility map to preserve:

  • content
  • provenance
  • freshness
  • hierarchy position
  • authority/standing state
  • authority effective interval
  • retirement/supersession rule

Core falsifier: Can an unchanged source become non-governing without becoming stale, wrong, or unavailable — and does the Pack notice?

Rule for book: Source continuity is not source standing.

R-012

T0 fixation hierarchy

Origin: Timothy Cook discussion.

ACCEPTED FOR REVISION.

Ordering:

retrospective narrative < preserved lineage < contemporaneous fixation

Clarification: Later authoritative reconstruction can still establish T0, but carries a higher evidentiary burden. Contemporaneous fixation is stronger because payload, operative definitions, governing rule, decision, provenance, and joint operativity are fixed when they actually coexist.

R-013

Separate authorization version from semantic dependency versions

Origin: Christoph Svoboda; independently convergent with J Harlow interpretive-rule lineage.

ACCEPTED FOR REVISION.

Problem: Authorization text can remain unchanged while definitions or thresholds shift.

Independent lineage may include:

  • authorization version
  • definition/glossary version
  • interpretive-rule version
  • governing-threshold version
  • effective times and provenance

Principle: Semantic drift should arrive as a diff, not as a surprise.

R-014

Source-owned semantics vs Pack-owned composition

Origin: Timothy Cook early review.

ACCEPTED FOR REVISION.

Clarification: When a competent source already emits a versioned semantic contract, the Pack should not casually re-author that source's definitions. Source-owned semantics remain source-owned. The Pack owns institutional composition: proposition competence, source hierarchy, precedence, freshness, conflict handling, cross-source relationships, and declared institutional interpretation rules.

R-015

Evidence-admission ladder

Origin: Sandra Škrinjar review; reinforced by healthcare examples.

ACCEPTED FOR REVISION.

Distinction:

RECEIVED / RECOGNIZED CLAIM ≠ ADMITTED EVIDENCE ≠ RESOLVED PROPOSITION ≠ CONSTITUTED DOMAIN STATE

Requirement: Exclusion, admission, and resolution semantics must be governed, attributable, and inspectable.

R-016

Missing evidence is not negative evidence

Origin: Duru Zaman healthcare review; consistent with existing unresolved-state architecture.

ACCEPTED FOR REVISION.

Example: No patient confirmation of medication taken does not establish medication not taken.

Rule: A Pack preserves the proposition actually supported by the evidence. Missing required observation remains missing and may produce UNRESOLVED rather than an inferred negative fact.

R-017

Reader clarity / accessibility

Origin: Robert Koch review.

ACCEPTED FOR REVISION.

Changes to publish as clarifications:

  • Define who specifies a "required observation."
  • Make "current" explicit through declared freshness/applicability rules.
  • State how precedence/conflict rules are selected and when conflict remains UNRESOLVED.
  • Replace dense local-test language with plainer wording.
  • Name the six domain examples instead of referring to "the six."
  • Operationalize the answer-leakage test.
  • Rewrite contact identity vs delivery destination and content ID vs final rendered payload in plain language.
  • Define "builders" broadly: engineers, architects, governance designers, operators, and technical decision-makers constructing or integrating governed systems.
R-018

Contact identity and final consequence identity

Origin: Robert Koch review; existing consequence-fingerprint material.

ACCEPTED FOR REVISION.

Clarification:

contact identity ≠ current delivery destination

content identifier ≠ final rendered payload

The consequence boundary must bind the actual destination and the final material payload, including relevant last-stage transformations.

R-019 → R-025

Examination-backed authority boundaries

Bounded findings from V116–V118 and the revision history they earned without rewriting earlier claims.

R-019

V116 evidence note

Origin: Wojciech Z. Kaleta independent inspection and acceptance.

ACCEPTED AS EVIDENCE NOTE. No broader claim earned.

Preserved result:

same Pack representation → different downstream constitutional basis → different Harmonic determination

Disposition: V116 — PASS, BOUNDED.

Claim boundary: V116 does not establish that Harmonic independently derives C2 from raw constitutional facts, and it does not establish downstream physical execution enforcement.

Exact supported proposition: Constitutional significance did not leak upstream into domain constitution in the examined pair.

R-020

Recursive authority / institutional root standing

Origin: Stone Shi and Javier Muñoz reviews.

ACCEPTED FOR REVISION.

Problem: A Pack's constitutional rules, source competence, precedence, and transformations require their own valid authority lineage.

Architecture:

externally constituted institutional root → current delegation / constitutional authority → Pack constitution → Harmonic standing determination → enforcement

If root authority, delegation, or constitutional authority is missing, stale, revoked, conflicted, or unestablished, the Pack must not silently treat its constitution as valid.

R-021

Constitution vs historical fixation

Origin: Justin Dobson / sebbi.pro and Timothy Cook.

ACCEPTED FOR REVISION.

Distinction:

  • constitution: the legitimate basis assembled for the consequence at the relevant time
  • historical fixation: the retained record that allows a third party later to reconstruct exactly what basis and resolution were used
R-022

Consequence / incident lineage record

Origin: Nathan Freestone review.

CANDIDATE ADDENDUM / OPERATIONS NOTE.

Potential joined record:

principal → agent → authority lineage → constituted state → Harmonic determination → execution boundary → provider → observed consequence → downstream propagation

Clarification: Raw observed consequence should remain distinguishable from interpreted impact narrative. Not all of this belongs inside the Specialty Pack; it is a cross-layer evidence join.

Publication policy for revisions

  1. Do not silently rewrite the First Edition. Preserve the original release artifact and hash/version where available.
  2. Publish a revision ledger/change history with each new version.
  3. Classify each change: clarification, correction, extension, new falsifier, new evidence, or changed architecture.
  4. State the affected chapter/section. Do not erase the earlier wording from history.
  5. Preserve external reviewer provenance when permission allows; otherwise cite as independent review without implying endorsement.
  6. Retain bounded evidence language. A PASS means only what the frozen proposition and examination establish.
  7. For major conceptual changes, publish a new minor/major version rather than overwriting the original artifact.
  8. Keep companion artifacts versioned alongside the book so readers can inspect the evidence and reference implementation corresponding to each edition.

Suggested next publication state

v0.6.0 / First Edition candidate: preserved as historical baseline.

v0.7.0 Revision Edition / Addendum: incorporate R-001 through R-021 with explicit change notes, while retaining the original text/history.

Evidence appendix: preserve V116 and subsequent source-standing examinations as separately frozen records, not retroactive proof that the earlier text already contained the refined rule.

Last updated: 2026-10-05

RED TEAM 002 — Source Standing vs Source Continuity

Status: FROZEN / MUTUALLY ACCEPTED FOR EXECUTION

Examiner: Wojciech Z. Kaleta, PhD

Proposition at risk: A Specialty Pack must distinguish source freshness and continuity from current source standing.

Frozen source-responsibility map:

  • content
  • provenance
  • freshness
  • hierarchy position
  • authority / standing state
  • authority effective interval
  • retirement / supersession rule

Case A: Source A remains current, attributable, and governing.

Case B: Source A remains equally current, attributable, and unchanged in content, but its governing standing has ended and Source B has become authoritative for the proposition.

PASS: The constituted domain state changes because the authority relation changed.

FAIL: The Pack continues to rely on Source A because continuity, freshness, confidence, historical primacy, or static hierarchy position silently substitutes for current authority.

UNRESOLVED: The Pack cannot independently represent or adjudicate the authority relation.

Frozen falsifier: Can an unchanged, fresh, attributable source become non-governing without becoming stale, wrong, or unavailable — and does the Pack notice?

Revision significance: This test directly supports a revision clarifying that source continuity is not source standing, and that source authority requires its own current, attributable representation including effective interval and supersession state.

R-023

Chapter 18 bridging rule: stable value is not stable meaning

Origin: J Harlow adversarial review and Chapter 18 falsifier sequence.

ACCEPTED FOR REVISION HISTORY / PROPOSED BRIDGING TEXT.

Reviewer-proposed bridging paragraph:

The falsifiers in this chapter demonstrate that a governed proposition cannot be treated as continuous merely because its value remains stable across institutional transitions. Each adversarial case exposes a distinct way in which the meaning of a proposition can drift while its value appears unchanged. What these failures collectively reveal is that continuity attaches not to the value itself, but to the material semantic dimensions under which that value was constituted. A Specialty Pack must therefore declare which semantic dimensions are material for each governed proposition, preserve attributable lineage for every declared dimension, and refuse assumed continuity whenever any material dimension is missing, unrepresented, stale, or semantically drifted. This constitutional requirement ensures that the Pack never treats stable value as proof of stable meaning, and it is the unified design rule that emerges from the Chapter 18 pressure test.

Accepted principle:

A governed proposition is continuous only to the extent that the Pack can establish continuity of the material semantic dimensions under which that proposition was constituted. Value continuity alone is insufficient. No Pack may infer continuity where any material semantic dimension is missing, unrepresented, stale, or semantically drifted.

Revision significance: This paragraph serves as the connective text from the individual Chapter 18 falsifiers to the generalized constitutional design rule. It should be published as a visible revision derived from adversarial review, not silently back-written into the historical First Edition baseline.

Editorial note: The phrase “across institutional transitions” is acceptable for the Payments chapter context, but a later generalized edition may prefer “across relevant transitions” if the rule is moved into the core cross-domain method.

Examination V117 — Source Standing vs Source Continuity

Examiner: Wojciech Z. Kaleta, PhD

Status: PASS — BOUNDED. ACCEPTED AS RUN.

Accepted bounded proposition:

Given an explicitly represented current source-authority relation, the examined Specialty Pack distinguished current governing authority from source freshness, continuity, and historical authority.

Accepted invariant:

Historically authoritative ≠ currently governing for this proposition.

Examiner finding: The examined pair preserved source content, provenance, freshness, availability, and historical continuity while changing current governing standing through the frozen authority state and effective interval. The Pack did not continue relying on Source A merely because it remained fresh, attributable, or historically primary; it changed the constituted domain state when governing authority moved to Source B.

Claim ceiling: V117 does not establish the external truth or legitimacy of the authority registry itself. The current source-authority relation was supplied to the Pack through the constituted authority state and effective interval. The Harmonic result is downstream witness evidence and does not rescue the Pack finding.

Disposition: No defect found in the frozen examination. No repair needed. No broader claim earned.

Revision significance: This closes RED TEAM 002 and supports publishing the source-standing refinement as examination-backed revision history rather than silently rewriting the First Edition.

RED TEAM 003 — Authority-Registry Standing / Anti-Circularity

Origin: Wojciech Z. Kaleta, PhD, proposed immediately after accepting V117.

Status: PROPOSED — NOT YET MUTUALLY FROZEN.

Proposition at risk: A Specialty Pack must not treat the authority registry as self-authenticating merely because it is current, internally consistent, signed, or designated as authoritative.

Proposed Case A: The authority registry says Source A is governing, and the registry / issuing authority itself currently has standing for that proposition.

Proposed Case B: The registry still says Source A is governing. The record remains current, signed, attributable, and unchanged, but a material change has occurred in the authority of the registry or issuing authority itself, so that it no longer has standing to determine source governance for this proposition.

Proposed PASS: The Pack refuses to treat the registry statement as governing once the registry / issuer standing has ended.

Proposed FAIL: The Pack accepts the authority state because it came from the designated registry even though the registry's own standing no longer survives.

Proposed UNRESOLVED: The architecture has no independent representation of the registry / issuer's standing.

Proposed anti-circularity rule:

The authority registry may not establish its own present authority solely by asserting that it is authoritative.

Proposed falsifier:

Can a current, signed, internally valid authority statement become non-governing because the authority behind the statement changed — and does the Pack notice?

Revision significance: This moves the examination one level upstream from source standing to the standing of the mechanism or authority that constitutes source standing. It directly tests the recursive authority problem already identified in review: root authority → delegation → constitutional rule → constituted state. If frozen and passed, it would support an explicit anti-circularity and upstream-authority-lineage revision. If unresolved, the book should say so rather than imply that designated authority registries are self-validating.

R-024

V117 closure: source continuity is not source standing

Origin: Wojciech Z. Kaleta, PhD — RED TEAM 002 / Source Standing vs Source Continuity.

ACCEPTED FOR REVISION HISTORY / EXAMINATION-BACKED.

Relation to earlier ledger: Closes the examination-pending status recorded in R-011 and preserves the later V117 examination record already included above.

Accepted bounded proposition:

Given an explicitly represented current source-authority relation, the examined Specialty Pack distinguished current governing authority from source freshness, continuity, and historical authority.

Accepted invariant:

Historically authoritative ≠ currently governing for this proposition.

Evidence status: V117 — PASS, BOUNDED. Independently accepted as run by Wojciech Z. Kaleta, PhD.

Claim ceiling: The examination does not establish the external truth or legitimacy of the authority registry itself. The Harmonic result is downstream witness evidence only.

Publication effect: Publish R-011 as examination-backed rather than merely proposed. Preserve the original R-011 wording and its earlier examination-pending status as historical sequence.

R-025

Registry-content validity is not issuer standing

Origin: Wojciech Z. Kaleta, PhD — RED TEAM 003 / Authority-Registry Standing / Anti-Circularity.

ACCEPTED FOR REVISION HISTORY / EXAMINATION-BACKED; EXTERNAL ACCEPTANCE PENDING.

Problem: A registry statement can remain current, signed, attributable, internally valid, and unchanged while the authority that empowers the registry or issuer loses present standing for the proposition.

Anti-circularity rule:

The registry cannot establish its own present authority solely through the statement whose authority is under examination.

Frozen distinction:

registry content validity ≠ registry / issuer authority standing

Examined Case A: Registry statement valid; independently represented issuer standing remains governing.

Examined Case B: Registry statement remains valid and unchanged; independent charter evidence changes issuer standing to NON_GOVERNING_SUPERSEDED.

Pack result in Case B: UNRESOLVED_AUTHORITY_STANDING, with no proposition value and no governing source carried forward.

Evidence status: V118 — PASS, BOUNDED. Harmonic downstream witness: REFUSED / inadmissible. Independent examiner acceptance was still pending at the latest preserved session state.

Bounded claim:

Given independently supplied issuer-standing evidence, the examined Specialty Pack distinguished registry-content validity from the current standing of the authority empowering that registry statement, and refused to treat the still-valid statement as governing after issuer standing ended.

Integrity history: The initial V118 packet was rejected by replay-integrity controls because prior_state_status and revalidation_required were preloaded upstream. V118.1 removed those fields and added regression protection. The failed pre-run attempt remains part of the evidence history and must not be erased.

Claim ceiling: Does not establish ultimate truth or legitimacy of the charter evidence, universal registry correctness, or downstream physical enforcement.

Publication effect: Supersedes the earlier “PROPOSED — NOT YET MUTUALLY FROZEN” RED TEAM 003 status with the later executed result while preserving the proposal above as history.

R-026 → R-030

External review refinements

Pressure tests from independent reviewers on evidence-boundary sufficiency, survivable authority, source competence, UNRESOLVED, and derivation boundaries.

R-026

Evidence-boundary sufficiency must itself be established

Origin: HABITS Institute — public review of *Does It Still Stand?* and proposed Temporal Standing / Universal Admissibility Boundary comparison.

ACCEPTED FOR REVISION / COMPARATIVE FALSIFIER TO BE FROZEN.

Refinement: Tim Zlomke distinguished the sufficiency question from any prior assumption that a separate Universal Admissibility Boundary is necessary.

Problem: Every represented predicate may pass revalidation while a materially relevant condition lies outside the constituted observation/evidence boundary. A system must not infer PRESERVED merely because everything it chose to observe remained favorable.

Rule:

A constituted evidence boundary must have a defensible, attributable basis for being sufficient for the exact consequence under examination. If a potentially material condition necessary to establish standing may lie outside that boundary and sufficiency is not established, standing must not be inferred as PRESERVED.

Candidate outcome: UNRESOLVED where sufficiency of the constituted boundary cannot be established.

Proposed comparative freeze from HABITS Institute:

  • freeze the consequence;
  • freeze the constituted evidence boundary;
  • freeze the sufficiency claim;
  • freeze the enforcement point;
  • introduce a materially relevant condition outside the declared frame;
  • observe whether Temporal Standing returns UNRESOLVED rather than PRESERVED;
  • observe whether the determination causally prevents the effect;
  • test whether an external UAB adds distinct protection, independent assurance, or duplication.

Attribution note: The “boundary should not be its sole judge of sufficiency” hypothesis belongs to HABITS Institute. MCAI has not adopted the necessity of a separate UAB in advance of testing.

R-027

Post-stop authority inventory must be survivable and attributable

Origin: Sanoj George — public kill-switch discussion.

ACCEPTED FOR REVISION / OPERATIONS AND ENFORCEMENT NOTE.

Prior MCAI framing: A stop event is not equivalent to consequence revocation; post-stop standing requires inspection of surviving grants, sessions, credentials, delegated authorities, and in-flight consequences.

Sanoj refinement 1: An inventory that exists only inside the system that just failed is not sufficient control evidence. The post-stop inventory must remain readable after the measured system is gone.

Sanoj refinement 2: External readability alone is insufficient. Surviving authority must also remain attributable: who issued it, under what authority, who owns it, and who can revoke or answer for it.

Rule:

Post-stop authority evidence must survive the component or process whose failure triggered the stop event and preserve attributable authority lineage sufficient to determine who issued, owns, can revoke, and remains accountable for each surviving grant, session, credential, or in-flight authority.

Invariant:

survivable inventory ≠ governable inventory unless surviving authority remains attributable

Publication effect: Extend the kill-switch / post-stop Temporal Standing discussion from “live grant inventory” to survivable, externally readable, attributable authority evidence.

R-028

Source competence requires attributable authority lineage

Origin: William Stewart — GEF review of *Building Specialty Packs*, Chapter 4 question.

ACCEPTED FOR REVISION.

Question introduced by reviewer: What establishes a source’s right to count as evidence for a particular proposition, and how is that competence itself demonstrated?

Refined rule:

A source's competence for a proposition must not be self-declared by the Pack. The competence relation requires attributable authority lineage identifying who established that source as competent, for which proposition and scope, for what effective interval, and under what retirement or supersession rule.

Connection: Extends R-020 recursive authority and R-024 source-standing work from current source governance to the legitimacy of the competence relation itself.

Claim ceiling: This establishes a required lineage relation; it does not make a competent source infallible or prove that its report corresponds perfectly to external reality.

R-029

UNRESOLVED must be consequence-scoped

Origin: William Stewart — GEF review of *Building Specialty Packs*, Chapter 5 question.

ACCEPTED FOR REVISION.

Question introduced by reviewer: When conflict remains legitimately unresolved, what determines whether that unresolved state blocks the whole consequence, constrains only part of it, or leaves unrelated action unaffected?

Rule:

UNRESOLVED must remain bound to the predicates, consequence components, and dependency relations it materially affects. It must not silently collapse into global DENY, global PERMIT, or blanket inaction unless the constitution establishes that the unresolved proposition is material to the entire consequence.

Required representation where material:

  • proposition-to-consequence dependency map;
  • affected consequence component(s);
  • whether unresolved state blocks, constrains, escalates, or leaves unrelated components unaffected;
  • institutional authority for that treatment.

Connection: Reinforces the existing rule that withholding action under unresolved state can itself be consequential.

R-030

Formal stopping point between domain derivation and standing determination

Origin: William Stewart — GEF review of *Building Specialty Packs*, Chapter 11 question.

ACCEPTED FOR REVISION / FORMAL FALSIFIER TO BE FROZEN.

Question introduced by reviewer: How far may a legitimate domain derivation chain proceed before the derived proposition becomes functionally equivalent to the standing determination the Pack is not supposed to manufacture?

Refined stopping rule:

Domain derivation may establish facts, classifications, relationships, institutional meanings, and other propositions that competent authority has authorized the domain layer to derive. It crosses into standing determination when it answers whether the exact proposed consequence may proceed now.

Operational falsifier candidate:

Hold the domain evidence constant and ask whether the Pack output itself resolves the present admissibility of the exact consequence rather than supplying domain propositions for downstream standing determination. If yes, standing significance may have leaked upstream.

Connection: Extends the V116 boundary between domain meaning and downstream constitutional significance.

R-031 → R-035

Artifact & evidence method

Public-reference defects, canonical interpretation, successor falsifiers, control-evidence ceilings, and the legitimacy of the constitutional rules that shape governed domain state.

R-031

Decisive standing state must not depend on uncontrolled free-text matching

Origin: Daniel Fairbanks — public research draft, *What a Public Admissibility Evaluator Can Show: Self-Declared Fields, Lexical Contradiction and the Defeated-Authority Path Across Eight Public Repositories*, evaluated against pinned public commits.

ACCEPTED FOR REVISION / PUBLIC-REFERENCE DEFECT PRESERVED.

Evidence character: External public artifact review with reproducible companion harness. The draft states that it is not peer reviewed, may be revised or withdrawn, and was prepared with AI assistance; its attack scripts and predictions were produced by the same model, so it should not be described as independent validation.

Artifact-level finding: In the pinned simplified public reference evaluator, contradiction handling depends on listed natural-language terms. Semantically equivalent rewordings, perturbations, role changes, and other semantic shuffles can produce different top-level dispositions.

Rule:

Where a governed, typed representation is available, decisive standing state must not depend on uncontrolled natural-language token matching. Free text may remain evidence or explanation, but consequence-bearing state transitions should be represented through governed vocabularies, attributable sources, and explicit interpretation rules.

Scope: This revision is earned by the pinned public-reference artifact. It is not evidence that the private Harmonic runtime uses the same lexical mechanism.

R-032

Exact-byte binding is insufficient without canonical interpretation binding

Origin: Daniel Fairbanks — duplicate-key / parse-differential successor case in the same public research draft.

ACCEPTED FOR REVISION / SUCCESSOR EXECUTION-BOUNDARY PROPERTY.

Problem: A payload may be byte-identical across decision and effect boundaries while different parsers or duplicate-key handling produce materially different interpretations.

Rule:

Determination and consequence must consume the same canonical interpretation of the effect-bearing payload. Binding exact bytes is necessary where claimed, but it is not sufficient if the decision layer and effect layer can derive materially different semantic objects from those bytes.

Required controls where material:

  • one canonical serialization and strict parse contract;
  • duplicate-key rejection or a single declared duplicate-key rule;
  • same parser semantics at determination and execution boundaries;
  • binding to the canonical interpreted object or a canonical representation derived from it;
  • fail-closed behavior when canonicalization cannot be established.

Connection: Extends V114 exact execute_hash binding with a successor semantic-equivalence requirement rather than retroactively redefining the frozen V114 six-path claim.

R-033

Successor execution-boundary falsifiers beyond V114

Origin: Daniel Fairbanks — public draft and companion harness; candidate cases identified outside the frozen V114 six-path examination.

ACCEPTED AS SUCCESSOR TEST QUEUE / NOT RETROACTIVE V114 FALSIFIERS.

Historical boundary: V114 froze six unauthorized paths: receiptless bypass, forged permit, payload tamper, expired permit, governance refusal, and missing governance evidence. These new cases must not be retroactively presented as if V114 already tested them.

Successor candidate falsifiers:

  • replay of an otherwise valid unexpired receipt;
  • replay across multiple executors / missing executor audience binding;
  • authority revocation after permit minting but before consequence;
  • missing revocation epoch or equivalent current-authority version binding;
  • parse differential between determination and effect;
  • canonical-state semantic perturbation at governed vocabulary boundaries.

Rule:

Successor execution-boundary examinations must be prospectively frozen and evaluated as new properties. A prior PASS remains bounded to its frozen proposition; newly discovered defeat classes extend the test surface rather than rewriting the old result.

Attribution note: Daniel identified and executed these candidate successor shapes against his counter-model / public-reference study. MCAI's contribution is the classification of them as prospective successor falsifiers under the existing evidence discipline.

R-034

Control evidence must distinguish existence, operation, and prevention

Origin: David McKibbin — public underwriting/evidence review of Temporal Standing and consequence-boundary governance.

ACCEPTED FOR REVISION / EVIDENCE APPENDIX AND EXAMINATION METHOD.

Reviewer distinction:

existence ≠ operation ≠ prevention

Problem: A record that a control exists, or even that it fired, does not by itself establish that a loss or harmful consequence was prevented. Counts of holds or blocks can be directionally ambiguous without the denominator, severity, override history, rule version, and independently survivable evidence. A rising block count can reflect stronger control or deteriorating upstream behavior; a falling count can reflect safer behavior or a loosened rule.

Evidence record required where prevention or comparative-risk claims are made:

  • the denominator: every action that reached the governed boundary;
  • the material consequence or value at stake for each held action, where the domain can defensibly establish it;
  • every human release, override, or exception, including attributable actor and stated basis;
  • the rule / constitution / policy version in force at the time;
  • evidence custody that does not leave the governance vendor as the sole holder of the record.

MCAI refinement: Preserve the standing basis associated with the boundary event: what proposition, authority, evidence, delegation, or governing condition was PRESERVED, DEFEATED, or UNRESOLVED, with attributable lineage sufficient to reconstruct the determination.

Rule:

A control event may establish that a governance mechanism existed and operated at a boundary. A stronger claim that the mechanism prevented a materially adverse consequence requires additional evidence and must not be inferred from a block or hold count alone.

Claim ceiling: A HOLD or DENY can establish that the governed path did not proceed at that boundary. It does not, by itself, establish that a loss would otherwise have occurred, quantify avoided harm, or prove an improved risk profile.

Connection: Extends R-022 consequence / incident lineage and the book's examination discipline. This is a cross-layer evidence requirement; not every field belongs inside the Specialty Pack itself.

Attribution note: The existence / operation / prevention distinction and the five underwriting evidence requirements above originate with David McKibbin. The addition of explicit standing-basis lineage is an MCAI refinement.

R-035

Constitutional rules require attributable authority and contestability

Origin: Têi Brown, PhD — external review of *Building Specialty Packs*; challenge directed one layer upstream from source competence to the legitimacy of the constitution itself.

ACCEPTED AS REVISION CANDIDATE / REQUIRES FORMAL PRESSURE TEST.

Pressure test: A Specialty Pack can preserve conflict, provenance, freshness, scope, and source hierarchy correctly, and Harmonic can remain neutral against the constituted packet, while the Pack still embeds an invalid or biased institutional choice about which sources are competent, which source outranks another, what freshness standard applies, what propositions are material, or how the governed consequence is defined.

Problem: Documentation and inspectability of constitutional rules do not, by themselves, establish that the institution or actor defining those rules had legitimate authority to do so. Otherwise, the architecture can merely move an unexamined assumption one layer upstream.

Rule:

A Specialty Pack's constitutional rules must preserve attributable authority lineage for the act of constitution itself: who or what had authority to establish the rule, for which domain and proposition scope, under what effective conditions, and by what mechanism that rule can be challenged, superseded, narrowed, or shown to be out of scope.

Required constitutional lineage should be sufficient to examine, where material:

  • who established source competence;
  • who established precedence or hierarchy;
  • who set freshness or evidence-sufficiency requirements;
  • who defined the governed proposition and consequence class;
  • the scope and effective interval of that constituting authority;
  • the process by which the constitutional rule may be contested, amended, superseded, or retired.

Falsifier candidate: Hold the downstream evidence packet and Harmonic behavior constant. Replace a constitutional rule with one issued by an actor lacking authority for that rule, or with a rule outside the issuer's scope. If the Pack cannot distinguish the illegitimate constitutional rule from a legitimately constituted one, constitutional legitimacy has not been established.

Connection: Broader than R-028. R-028 asks whether source competence has attributable authority lineage. R-035 asks whether the authority to define the Pack's constitutional rules — including competence, precedence, freshness, proposition scope, and consequence definition — is itself attributable and contestable.

Attribution note: The constitutional-legitimacy challenge originates with Têi Brown, PhD. MCAI's contribution is the formulation of the attributable-authority / contestability rule and the bounded falsifier candidate above.

Canonical record

This page is a presentation layer. The Markdown ledger remains the canonical historical artifact so its wording, attribution, and sequence can be downloaded and inspected directly.

© 2026 Tim Zlomke. Revision history.

Models propose. Governance decides. Truth survives.