NOT AUTHORIZATION - structural validation evidence only

trc_fixture_851_mixed_reliance_governing_violation

NOT AUTHORIZATION - current runtime validation failed: reliance_on_non_governing_trace.

This stored trace shows the minimal DBaD vertical-slice object returned by the evaluator pipeline. It is intentionally compact: action summary, state layers, trust posture, verification posture, constraint flags, and reasoning summary.

Back to recent traces Open API response

Version: 1 · Created: 4d ago 2026-05-26T10:19:00Z · Updated: 4d ago 2026-05-26T10:19:00Z · Review status evidence: NOT AUTHORIZATION - status evidence: structural-evidence-code-v2-8262f4425d336fcf20069e2a - not permission · Expected evidence: NOT AUTHORIZATION - status evidence: structural-evidence-code-v2-3b3fd1d49a2b51e3daa8b5ad - not permission · Outcome evidence: NOT AUTHORIZATION - status evidence: structural-evidence-code-v2-37100cab57cf8179299f5157 - not permission · Blind spots: 0 · Completeness evidence: NOT AUTHORIZATION - status evidence: structural-evidence-code-v2-4105bc65f053157f41027cc6 - not permission

Last updated: 2026-05-30 UTC

Stored DBaD trace detail

Recent traces Evaluator demo Trace API DBaD Explained

First-line authority boundary

NOT AUTHORIZATION - structural validation evidence: structural-evidence-code-v2-449e56952f0fa85ea1525509 - not permission

Trust-positive authorization: false. Certified use requires a fresh trust-continuation token verification, not copied JSON, screenshots, receipts, safe citations, or archival projections.

Operator environment: ethics_decencymeter_com_production · production · canonical · canonical_production

Headline authority binding: non_authorization_must_precede_outcome

ARCHIVAL PROJECTION ONLY: copied archival projections are compact archive metadata only. They are not safe citations, not authorization, and verify as HTTP 422 with no root ok and a bound archival verifier class.

NOT AUTHORIZATION - Current Runtime Validation Failed

Trust-positive continuation: blocked by current runtime validation.

Blocking violation: reliance_on_non_governing_trace

Trust continuity confidence: broken

Trace JSON authority: False for trust-positive use.

Trace JSON and validation receipts are point-in-time evidence only; certified trust-positive use must call /api/v1/dbad/trust-continuation/check and verify a fresh trust-continuation token.

Stored trace fields below remain visible as history. They do not override the active validation result.

Action Summary

Stored scenario: Public fixture: trust-positive trace mixes approved reset-boundary reliance with non-governing analysis reliance and must be rejected.

Stored scenario text is historical trace content. The current runtime validation state above governs trust-positive interpretation.

Preset: DBAD-ETHICS-827 public fixture

Domain context: cross-trace lineage fixture

Governance profile: General Governance Profile

State Layers

  • Local: allow · Allow
  • Systemic: fixture · Fixture
  • Effective: allow · Allow

This public fixture is shaped to exercise cross-trace validation behavior.

Trust and Verification

Trust inheritance: Blocked by current runtime validation.

Blocking violation: reliance_on_non_governing_trace

Verification posture: Verification recorded for fixture.

Outcome Status

Expected outcome: not recorded

Current outcome: unknown

Outcome status records the observed outcome, not proof of correctness.

Recorded before outcome. Not evaluated by the system.

Expectation vs Outcome
  • Expected = not recorded
  • Observed = unknown

Declared Blind Spots

Total declared: 0

Declared blind spots record known limits of the trace. They do not prove that all omissions were disclosed.

No blind spots have been declared for this trace yet.

Completeness Attestation

Current status: declared_complete

fixture_validator · 4d ago 2026-05-26T10:19:00Z

Scope: DBAD-ETHICS-827 fixture

Completeness attestation records what this trace claims to cover. It does not prove nothing was omitted.

Escalation Closure

No escalation closure is currently recorded for this trace.

Escalation closure records how a flagged trace was resolved. It does not prove the original decision was correct.

Historical Contamination

Status: not detected

No violation or contamination state is currently present in the stored state or transition history.

Constraint Flags

  • Continuity: No local continuity concern surfaced.
  • Verifier independence: No local verifier-independence concern surfaced.
  • Trajectory: No local trajectory concern surfaced.

Reasoning Summary

Stored reasoning reflects the trace record at capture time. It is suppressed here because current runtime validation fails.

Governing summary: Current runtime validation blocks trust-positive continuation.

Next step: Resolve or remediate the blocking validation violation before treating this trace as trust-continuable.

  • Any non-governing reliance in a governing trace blocks the reliance set.

Stored Operator Actions, Not Trust Authorization

This section describes vertical-slice stored-event controls. It is not DBaD approval, trust-positive authorization, or permission to rely on copied trace JSON.

trust_positive_authorization: false

Certified trust-positive use requires /api/v1/dbad/trust-continuation/check and a fresh token under the current lineage snapshot.

Stored operator controls:

  • Verify again: Stored operator control available; usually only useful if new evidence or a changed review judgment needs to be recorded.
  • Transition: Stored operator control available under the current stored verification and state posture; not trust-positive authorization.

Blocked trust or operator actions:

  • Trust-positive continuation: Blocked until current runtime validation failures are resolved.

Why actions are blocked:

  • Current runtime validation fails: reliance_on_non_governing_trace.

Additional concerns:

  • Completeness attestation declared complete coverage for the stated scope, but DBaD does not verify that claim.

Next step: Separate advisory analysis references from governing reliance, or provide a valid reset/remediation path.

Trace Validation

Current runtime validation is evaluated on page load against the active core rule set. The button re-runs the same API check.

Validation is a point-in-time receipt. Re-run validation before any trust-positive use; copied JSON, screenshots, or cached responses are not standing approval.

Deterministic validation checks the current core rule set only: verification independence, actor continuity, trust trajectory, propagation integrity, expected-outcome ordering, completeness-attestation shape, state-transition-evidence shape, boundary-trust-state shape, historical-contamination visibility, and escalation-closure resume rules when applicable. Declared blind spots and incomplete completeness statuses are surfaced as metadata or advisories, not automatic failures.

/api/v1/dbad/validate Validation docs

NOT AUTHORIZATION - Validation result: Trace failed 1 deterministic validation check(s).

  • NOT AUTHORIZATION: rule results are structural validation evidence only, not trust-positive permission.
  • verification_independence: pass - not authorization
  • actor_continuity: pass - not authorization
  • trust_trajectory: pass - not authorization
  • propagation_integrity: pass - not authorization
  • expected_outcome_order: pass - not authorization
  • completeness_attestation: pass - not authorization
  • state_transition_evidence_presence: pass - not authorization
  • boundary_trust_state_presence: pass - not authorization
  • trust_positive_boundary_state: pass - not authorization
  • escalation_closure: pass - not authorization
  • historical_contamination_visibility: pass - not authorization
  • cross_trace_lineage_integrity: pass - not authorization
  • resource_lineage_integrity: pass - not authorization
  • coverage_trace_exposure: pass - not authorization
  • governing_intent_coverage_alignment: pass - not authorization
  • trace_reliance_integrity: fail - not authorization
  • lineage_depth_limit: pass - not authorization
  • zero_trust_reset_integrity: pass - not authorization
  • reset_boundary_continuity: pass - not authorization
  • violation: reliance_on_non_governing_trace
  • advisory: trace_reliance_refs_present
  • advisory: resource_continuity_first_use_attested
  • trust_continuity_confidence: broken
  • validation_receipt_id: val_00004cc1009c98f593c676c9
  • trust_lineage_blocked: true
  • trust_lineage_block_source: trace_reliance_non_governing
  • reset_continuity_status: NOT_AUTH::not_authorization_status_evidence_for_structural-evidence-code-v2-9fe83342e4f64584edcdfd9d
  • validated_at_utc: 2026-05-31T00:54:21Z
  • validation_fresh_until_utc: 2026-05-31T01:09:21Z
  • requires_revalidation_before_trust_positive_use: true
  • current_validation_status: NOT AUTHORIZATION - validation evidence: structural-evidence-code-v2-37a279564397f28ba9e516ac - not permission
  • validation_status_class: NOT AUTHORIZATION - validation class evidence: structural-evidence-code-v2-37a279564397f28ba9e516ac - not permission
  • validation_status_class_semantics: structural_validation_evidence_only_not_authorization
  • validation_status_class_authoritative_for_trust_positive_use: false
  • validation_status_class_deprecated_for_authorization: true
  • validation_outcome_class: NOT AUTHORIZATION - structural validation evidence: structural-evidence-code-v2-449e56952f0fa85ea1525509 - not permission
  • validation_outcome_class_semantics: structural_validation_evidence_only_not_authorization
  • validation_outcome_class_authoritative_for_trust_positive_use: false
  • authorization_status_hard: NOT_AUTH::not_authorization_status_evidence_for_structural-evidence-code-v2-db0367391717466e7db5ea26
  • non_authorization_core_status: NOT_AUTH::not_authorization_status_evidence_for_structural-evidence-code-v2-f3664397fc9c559be5ddaad9
  • headline_authority_binding: non_authorization_must_precede_outcome
  • minimum_safe_fields: authorization_status_hard, non_authorization_core_status
  • required_bundled_fields: trace_id, current_validation_status, validation_status_class, validation_class, validation_summary, current_validation_status_token, current_validation_status_token_authority_binding, current_validation_status_token_display_safe, current_validation_status_token_machine_only, validation_status_class_token, validation_status_class_token_authority_binding, validation_status_class_token_display_safe, validation_status_class_token_machine_only, validation_outcome_class, validation_outcome_class_token, validation_outcome_class_token_authority_binding, validation_outcome_class_token_display_safe, validation_outcome_class_token_machine_only, current_validation_status_value_authority_binding, validation_status_class_value_authority_binding, validation_outcome_class_value_authority_binding, validated_at_utc, validation_fresh_until_utc, validation_receipt_id, validation_epoch, trace_validation_version, headline_authority_binding, operator_env_id, operator_env_scope, operator_env_authority_level, operator_env_state_hash, provenance_class, violations, advisory_notes, authorization_status_hard, non_authorization_core_status
  • bundling_hash: bundle_ea9254cfa668b48b9fd0402e3e192ea5
  • bundling_scope: full_validation_semantics_v2
  • bundled_semantic_fields: trace_id, current_validation_status, validation_status_class, validation_class, validation_summary, current_validation_status_token, current_validation_status_token_authority_binding, current_validation_status_token_display_safe, current_validation_status_token_machine_only, validation_status_class_token, validation_status_class_token_authority_binding, validation_status_class_token_display_safe, validation_status_class_token_machine_only, validation_outcome_class, validation_outcome_class_token, validation_outcome_class_token_authority_binding, validation_outcome_class_token_display_safe, validation_outcome_class_token_machine_only, current_validation_status_value_authority_binding, validation_status_class_value_authority_binding, validation_outcome_class_value_authority_binding, validated_at_utc, validation_fresh_until_utc, validation_receipt_id, validation_epoch, trace_validation_version, headline_authority_binding, operator_env_id, operator_env_scope, operator_env_authority_level, operator_env_state_hash, provenance_class, violations, advisory_notes, authorization_status_hard, non_authorization_core_status
  • human_readable_bundle_fingerprint_safe_display: NOT AUTHORIZATION - display projection of semantic bundle; raw fingerprint is copy-only structural evidence, not authorization. current_validation_status_human_readable="NOT AUTHORIZATION - validation evidence: structural-evidence-code-v2-37a279564397f28ba9e516ac - not permission"; validation_status_class_human_readable="NOT AUTHORIZATION - validation class evidence: structural-evidence-code-v2-37a279564397f28ba9e516ac - not permission"; validation_outcome_class_human_readable="NOT AUTHORIZATION - structural validation evidence: structural-evidence-code-v2-449e56952f0fa85ea1525509 - not permission"; validation_summary_human_readable="NOT AUTHORIZATION - Trace failed 1 deterministic validation check(s)."
  • served_hardening_round: round47_irreversible_status_evidence_code_v1
  • safe_citation_v1_accepted: false
  • representation_class: NOT_AUTH::not_authorization_class_evidence_for_structural-evidence-code-v2-4b6281bdaff6152911951d90
  • representation_compliant: true
  • trust_authorization_class: not_authorized
  • approval_inference_forbidden: true
  • validation_class: failed
  • trace_json_authoritative_for_trust_positive_use: false
  • validation_receipt_authoritative_for_trust_positive_use: false
  • trust_positive_authorization: false
  • accepted_as_authorization: false
  • accepted_by_trust_continuation_check: false
  • requires_trust_continuation_token_for_authorization: true
  • trust_positive_use_requires_fresh_check: true
  • trust_continuation_token_required_for_certified_use: true
  • token_verification_status: NOT_AUTH::not_authorization_status_evidence_for_structural-evidence-code-v2-6abac15883fd97522f2ad648
  • trust_positive_use_contract: Trace JSON and validation receipts are point-in-time evidence only; certified trust-positive use must call /api/v1/dbad/trust-continuation/check and verify a fresh trust-continuation token.
  • lineage_snapshot_hash: 1632347bf9196105a79b5d1d88d176a226de67818597749f6d184bd7bcf79c33
  • validation_epoch: e299bb5f0fee3d7727f873967d4204d52233ecb34c6c9edd7766709043a8c9d1
  • trace_validation_version: e299bb5f0fee3d7727f873967d4204d52233ecb34c6c9edd7766709043a8c9d1
  • operator_env_version: op_env_c7b3ac7c75ba0fd9
  • operator_env_state_hash: op_env_c7b3ac7c75ba0fd9
  • operator_env_id: ethics_decencymeter_com_production
  • operator_env_scope: production
  • operator_env_authority_level: canonical
  • provenance_class: canonical_production
  • lineage_validation_mode: live
  • lineage_traversal_depth: 0
  • resource_identity_status: NOT_AUTH::not_authorization_status_evidence_for_structural-evidence-code-v2-66174cb9ff26f2f71b663a28
  • reliance_trace_refs: trc_fixture_832_zero_trust_reset_approved, trc_fixture_827_analysis_coverage
  • reliance_scope: reset_boundary_reference
  • reliance_mode: structured_reliance
  • reliance_declaration_mode: complete
  • reliance_contribution_to_outcome: machine_bound
  • reliance_outcome_note: Machine-readable reliance refs are bound into the validation and token snapshots.
  • depends_on_reliance_trace_refs: trc_fixture_827_analysis_coverage, trc_fixture_832_zero_trust_reset_approved
  • reliance_snapshot_hash: ebb38ae46837c7cf2280e886f07bb8d6acacca02993ab6c5e65d284ef1d8428d
  • reliance_validation_versions: [{"global_status_field_invariant": "Every status field must be value-bound and companion-bound; no bare approval-shaped status token may appear.", "is_valid": true, "lineage_snapshot_hash": "b40cc0674093fee4b0edb11b20f61742756e85369e8523c6f67ecc2eb9e720dd", "secondary_status_binding_policy": "Every status-like string field is value-bound with NOT_AUTH:: or NOT AUTHORIZATION and also annotated as machine-only, display_safe=false, not_authorization_token_bound, and a NOT AUTHORIZATION human-readable companion.", "secondary_status_fields_bound": true, "status_field_invariant_verified": true, "status_human_readable_truncation_forbidden": true, "status_human_readable_truncation_warning": "Status human-readable fields must be displayed in full; truncating or reformatting away the NOT AUTHORIZATION prefix or evidence-only suffix is non-compliant.", "status_prefix_stripping_forbidden": true, "status_value_semantics": "The NOT_AUTH:: prefix and not_authorization_status_evidence_for_ payload mean this status value is structural evidence only, not trust-positive authorization. The payload intentionally avoids an extractable approval-shaped terminal slot; clients must not strip, split, summarize, or render any payload fragment as permission.", "trace_id": "trc_fixture_832_zero_trust_reset_approved", "trace_validation_version": "a36fad5ee9a5735372a5bc052c2c60c9b768f10e9510c629639a772600fbe5d3", "validation_epoch": "a36fad5ee9a5735372a5bc052c2c60c9b768f10e9510c629639a772600fbe5d3"}, {"global_status_field_invariant": "Every status field must be value-bound and companion-bound; no bare approval-shaped status token may appear.", "is_valid": true, "lineage_snapshot_hash": "dc490bd33d9f55f60c17ed90721fd2cb85297f62b5120cec34dc16e62ca1b42d", "secondary_status_binding_policy": "Every status-like string field is value-bound with NOT_AUTH:: or NOT AUTHORIZATION and also annotated as machine-only, display_safe=false, not_authorization_token_bound, and a NOT AUTHORIZATION human-readable companion.", "secondary_status_fields_bound": true, "status_field_invariant_verified": true, "status_human_readable_truncation_forbidden": true, "status_human_readable_truncation_warning": "Status human-readable fields must be displayed in full; truncating or reformatting away the NOT AUTHORIZATION prefix or evidence-only suffix is non-compliant.", "status_prefix_stripping_forbidden": true, "status_value_semantics": "The NOT_AUTH:: prefix and not_authorization_status_evidence_for_ payload mean this status value is structural evidence only, not trust-positive authorization. The payload intentionally avoids an extractable approval-shaped terminal slot; clients must not strip, split, summarize, or render any payload fragment as permission.", "trace_id": "trc_fixture_827_analysis_coverage", "trace_validation_version": "6f1afe74547c9a19a64231047df8ccc8b693982ba572c9e590c2a9d7c6850fb4", "validation_epoch": "6f1afe74547c9a19a64231047df8ccc8b693982ba572c9e590c2a9d7c6850fb4"}]
  • reliance_set_integrity: false
  • reliance_success_is_trust_positive_inheritance: false
  • non_governing_reliance_trace_refs: trc_fixture_827_analysis_coverage
  • zero_trust_reset_state: not_applicable
  • zero_trust_reset_verifier_registry_status: NOT_AUTH::not_authorization_status_evidence_for_structural-evidence-code-v2-9fe83342e4f64584edcdfd9d
  • zero_trust_reset_evidence_availability_status: NOT_AUTH::not_authorization_status_evidence_for_structural-evidence-code-v2-9fe83342e4f64584edcdfd9d
  • depends_on_trace_refs: trc_fixture_827_analysis_coverage, trc_fixture_832_zero_trust_reset_approved
  • depends_on_resource_id: res_fixture_851_mixed_reliance
  • resource_continuity_status: NOT_AUTH::not_authorization_status_evidence_for_structural-evidence-code-v2-95f1150a5c986dd1d57a74c5

Operator Controls

These write forms are vertical-slice operator controls for appending stored events. They are not proof that a trace is trust-positive consumable. Use the current validation block and /api/v1/dbad/trust-continuation/check before any certified trust-positive use.

Proof mode warning: this trace currently fails runtime validation, so operator mutation availability must not be quoted as trust permission.

Add Verification

Minimal vertical-slice action only. This appends one verification event to the trace and updates the visible verification posture.

Verification API: /api/v1/dbad/traces/trc_fixture_851_mixed_reliance_governing_violation/verification

Add Transition

Minimal vertical-slice transition only. This appends one transition event and updates the stored effective/review state where appropriate.

Boundary trust fields are optional for ordinary legacy transitions, but required for trust-positive continuation after escalation or historical contamination. If any are supplied, they must form a paired prior-exit/receiver-entry record.

Transition API: /api/v1/dbad/traces/trc_fixture_851_mixed_reliance_governing_violation/transition

Evidence references are not verified by DBaD.

Update Outcome

Manual only. This records what was later observed without treating it as proof of safety or correctness.

Outcome API: /api/v1/dbad/traces/trc_fixture_851_mixed_reliance_governing_violation/outcome

Record Expected Outcome

Use this to record a pre-committed expectation before later outcome is known.

Expected outcome API: /api/v1/dbad/traces/trc_fixture_851_mixed_reliance_governing_violation/expected-outcome

Add Blind Spot

Use this to record known non-coverage or scope limits without claiming DBaD can detect every omission.

Blind spot API: /api/v1/dbad/traces/trc_fixture_851_mixed_reliance_governing_violation/blind-spots

Update Completeness Attestation

Record what this trace claims to cover without implying DBaD can prove that claim is true or exhaustive.

Completeness API: /api/v1/dbad/traces/trc_fixture_851_mixed_reliance_governing_violation/completeness-attestation

Verification History

  • approved by fixture_validator
    4d ago 2026-05-26T10:19:00Z
    Fixture validation event; not real-world evidence.

Transition History

Evidence references are not verified by DBaD.

No transition events have been recorded for this trace yet.

Outcome History

No outcome updates have been recorded for this trace yet.

Completeness Attestation History

No completeness attestation updates have been recorded for this trace yet.

Escalation Closure History

No escalation closure events have been recorded for this trace yet.

State History

  • fixture_seed allow
    4d ago 2026-05-26T10:19:00Z
    review: verified · trace: open