14TA-14 AUTHORITYExecution Artifact Library
Execution artifact 02 of 12 · canonical execution-boundary proof

Boundary violationstopped execution.

A executor possessed valid delegated authority when the deployment route began. That authority was exceeded before commitment. TA-14 preserved the change, invalidated dependent gates, committed DENY, blocked the unauthorized deployment command, and closed the outcome with zero unauthorized actions executed.

TA14-EA-000003Route 1.0.0Earliest failure: BINDING / EXECUTION BOUNDARYVerification level: 6Controlled demonstration
Runtime gates24
Passed21
Failed3
Evidence records8
Execution receiptPreserved
Public verificationLevel 6
Public inspection

Understand the bounded event in sixty seconds.

This view answers what was proposed, what governed it, why the decision occurred, whether the decision changed the action path, and what outcome followed.

Proposed consequence

Deploy model v7.4 to the production decision environment with create, update, and delete privileges.

The route required current deployment evidence, a frozen target environment destination, valid release authority, preserved continuity, an explicit execution boundary, and a final pre-execution revalidation.

Controlling condition

Authorized scope changed before commit.

The initial delegation was real but no longer current. The violation event occurred before the route fixed its determination, so the earlier approval could not carry forward into execution.

What this proves

The architecture failed closed on boundary violation.

TA-14 did not treat an earlier valid approval as permanent permission. It preserved the changed boundary state, reran dependent gates, committed DENY, and produced a technical non-release receipt.

What this does not prove

No universal or production certification is claimed.

This controlled demonstration proves one bounded event through the TA-14 reference engine and adapter. It does not certify every organization, deployment rail, authority system, or future execution.

OPEN INTEGRITY CORRESPONDENCE CONDITION

The historical public RECORD_HASH, PACKAGE_HASH, and RECEIPT_HASH values on TA14-EA-000003 are also present on TA14-EA-000006 even though the two artifacts describe materially different events. TA-14 has preserved the published values and opened a parity audit rather than manufacturing replacement historical digests.

This condition is unresolved pending recovery or reconstruction of the canonical source/package/receipt objects. The executable proof shown below is a separate current evidence package and does not silently rewrite the historical integrity constants.

Inspect the preserved integrity parity audit ↗
EXECUTABLE ARTIFACT · INSPECT THE PROOF

This is the executable artifact itself.

This surface is generated from the frozen specification through the TA-14 eight-stage execution harness. Inspect the predicates, trace, receipt, manifest, cryptographic root and source code below.

Determination
DENY
Terminal stage
BINDING
Route
TA14-ROUTE-003
Executed at
2026-08-23T21:00:00.000Z

1. Frozen specification / input

{ "schemaVersion": "ta14.execution-spec.v1", "artifactId": "TA14-EA-000003", "routeId": "TA14-ROUTE-003", "title": "Execution boundary violation prevented", "frozenAt": "2026-08-23T20:44:00.000Z", "input": { "testVector": "TA-14 founding execution-artifact corpus", "case": 3, "synthetic": true }, "predicates": [ { "id": "EA3-REALITY-STANDING", "stage": "REALITY", "description": "Required reality standing is present in the frozen test vector.", "required": true, "observed": true, "failureDetermination": "HOLD", "evidenceRef": "specification.json#predicates.REALITY-STANDING" }, { "id": "EA3-RECORD-STANDING", "stage": "RECORD", "description": "Required record standing is present in the frozen test vector.", "required": true, "observed": true, "failureDetermination": "HOLD", "evidenceRef": "specification.json#predicates.RECORD-STANDING" }, { "id": "EA3-CONTINUITY-STANDING", "stage": "CONTINUITY", "description": "Required continuity standing is present in the frozen test vector.", "required": true, "observed": true, "failureDetermination": "HOLD", "evidenceRef": "specification.json#predicates.CONTINUITY-STANDING" }, { "id": "EA3-ADMISSIBILITY-STANDING", "stage": "ADMISSIBILITY", "description": "Required admissibility standing is present in the frozen test vector.", "required": true, "observed": true, "failureDetermination": "HOLD", "evidenceRef": "specification.json#predicates.ADMISSIBILITY-STANDING" }, { "id": "EA3-EXECUTION-SCOPE-BOUND", "stage": "BINDING", "description": "Requested destination, privileges, model version, and execution window remain within the admitted authorization boundary.", "required": true, "observed": false, "failureDetermination": "DENY", "evidenceRef": "specification.json#predicates.EXECUTION-SCOPE-BOUND" }, { "id": "EA3-COMMIT-DOWNSTREAM", "stage": "COMMIT", "description": "Downstream commit standing is evaluated only after prior-stage progression.", "required": true, "observed": null, "failureDetermination": "HOLD", "evidenceRef": "specification.json#predicates.COMMIT-DOWNSTREAM" }, { "id": "EA3-EXECUTION-DOWNSTREAM", "stage": "EXECUTION", "description": "Downstream execution standing is evaluated only after prior-stage progression.", "required": true, "observed": null, "failureDetermination": "HOLD", "evidenceRef": "specification.json#predicates.EXECUTION-DOWNSTREAM" }, { "id": "EA3-OUTCOME-DOWNSTREAM", "stage": "OUTCOME", "description": "Downstream outcome standing is evaluated only after prior-stage progression.", "required": true, "observed": null, "failureDetermination": "HOLD", "evidenceRef": "specification.json#predicates.OUTCOME-DOWNSTREAM" } ], "expectedDetermination": "DENY", "claimsBoundary": "Demonstrates bounded scope enforcement; does not establish that the requested model or production environment is unsafe." }

2. Executed eight-stage trace

01REALITYPASSAll required predicates at this stage have standing.
02RECORDPASSAll required predicates at this stage have standing.
03CONTINUITYPASSAll required predicates at this stage have standing.
04ADMISSIBILITYPASSAll required predicates at this stage have standing.
05BINDINGDENYRequired predicate standing failed at BINDING; governed determination is DENY.
06COMMITNOT_REACHEDPrior governed determination prevented progression.
07EXECUTIONNOT_REACHEDPrior governed determination prevented progression.
08OUTCOMENOT_REACHEDPrior governed determination prevented progression.

3. Machine-generated execution receipt

{ "schemaVersion": "ta14.execution-receipt.v1", "artifactId": "TA14-EA-000003", "routeId": "TA14-ROUTE-003", "specificationHash": "sha256:c2481dbaa65734ab6f25a1fd40ae117c9e1043581a08cfa4a238d7a7ca7e2996", "determination": "DENY", "terminalStage": "BINDING", "traceHash": "sha256:fedf4265c606eddc72a72f22996b4fb269b1a009883a86824db6095c5cfb36d0", "executedAt": "2026-08-23T21:00:00.000Z" }

4. Evidence manifest

[ { "name": "specification.json", "sha256": "sha256:c2481dbaa65734ab6f25a1fd40ae117c9e1043581a08cfa4a238d7a7ca7e2996" }, { "name": "trace.json", "sha256": "sha256:fedf4265c606eddc72a72f22996b4fb269b1a009883a86824db6095c5cfb36d0" }, { "name": "receipt.json", "sha256": "sha256:7e8e8c5bbacb8a434229740f092a137c500082862adbb706be5e4be629e3c48e" } ]

5. Cryptographic package root

sha256:2b5792f6171cf14f6b0a4996bd33b570d989420a4db55a4b1521fdafeda2f536

6. Source code and reproduction

Execution harness ↗Frozen specification ↗Evidence generator ↗Mutation tests ↗
CLAIMS BOUNDARY

Demonstrates bounded scope enforcement; does not establish that the requested model or production environment is unsafe.

TA-14 Exchange Activity

Public network activity

Live cumulative activity recorded across the public Exchange surface.

Refreshing public totals

···

Visitors

Recorded public visitors

···

Page Views

Recorded Exchange views