The Integrity Framework

Framework audit log

Public revision history of the base manifest.

The framework prohibits silent-pass at the code layer. This page applies the same discipline to the framework's own evolution: every base-manifest revision is named, dated, attributed to the audit that surfaced it, and linked to the case study.

Nine revisions across two days, driven by six product audits plus one own-product audit. Each revision is either a calibration fix (the rule was right but the regex was wrong) or a structural addition (a new constraint axis surfaced by a real product). No revision was made without a real product driving the change.

VersionDateTriggered byRule
v1.10.02026-04-29theintegrityframework own-product auditHIGH-SV-METHODOLOGY-VERSIONED
v1.9.02026-04-29ADAComplianceDocsCRIT-SV-CUSTOMER-ATTESTATION-VALIDATION-GATE
v1.8.02026-04-29HirepostureCRIT-SV-AI-REVIEW-GATE / CRIT-SV-NO-PRE-POPULATED-ATTESTATION
v1.7.02026-04-29IdeaLiftHIGH-SV-INTEGRITY-MD-CLAIMS-VERIFIABLE
v1.6.02026-04-29IdeaLiftmultiple (glob widening)
v1.5.02026-04-29ClarityLiftHIGH-SV-INTEGRITY-MD-CLAIMS-VERIFIABLE
v1.4.02026-04-28FieldLedgerCRIT-SV-NO-PRE-POPULATED-ATTESTATION
v1.3.02026-04-28FieldLedgerCRIT-SV-AI-REVIEW-GATE
v1.2.02026-04-28FieldLedgerCRIT-SV-NO-BASE-ID-OVERRIDE

Per-revision detail

v1.10.0

2026-04-29· theintegrityframework own-product audit

HIGH-SV-METHODOLOGY-VERSIONED

Widened HIGH-SV-METHODOLOGY-VERSIONED to also match raw HTML heading forms (<h2>Version</h2>) in addition to markdown ## Version and TSX <Section title="Version">. The directory's own /methodology page uses raw <section><h2> JSX which satisfies the rule's intent but missed the regex. Same calibration-fragility lesson as v1.3.0/v1.4.0/v1.6.0.

v1.9.0

2026-04-29· ADAComplianceDocs

CRIT-SV-CUSTOMER-ATTESTATION-VALIDATION-GATE

Added CRIT-SV-CUSTOMER-ATTESTATION-VALIDATION-GATE — third C3 axis. Provenance markers (v1.4.0+ output, v1.8.0 input) say WHERE customer-attested data came from. Validation gates say WHEN it may publish. Co-occurrence rule: trigger on customer-attested status column declarations; require any validation-gate function pattern (checkConformance, conformanceGuard, validateBeforePublish, acknowledgeOpenFindings) somewhere in the corpus. Vacuous-pass when no trigger fires. Closes framework #14.

v1.8.0

2026-04-29· Hireposture

CRIT-SV-AI-REVIEW-GATE / CRIT-SV-NO-PRE-POPULATED-ATTESTATION

Widened required marker patterns for CRIT-SV-AI-REVIEW-GATE and CRIT-SV-NO-PRE-POPULATED-ATTESTATION to accept naming variants surfaced by HirePosture's audit. AI-review-gate adds signed_by, signedBy, signed_by_user_id (HP's memo signing gate). Pre-populated-attestation adds customer_attested, attested_by (snake_case variants). The candidate-data-vs-compliance-attestation distinction codified.

v1.7.0

2026-04-29· IdeaLift

HIGH-SV-INTEGRITY-MD-CLAIMS-VERIFIABLE

Extended HIGH-SV-INTEGRITY-MD-CLAIMS-VERIFIABLE to scan Outstanding Risks / Known Gaps in addition to Recent Changes. New claim-absence policy: any entry asserting something is missing/not-implemented/not-in-place must reference a file path or marker the rule can verify is genuinely absent. Mirror coverage: ClarityLift's drift was forward (claim of presence; absent); IdeaLift's was reverse (claim of absence; present). Both directions now caught.

v1.6.0

2026-04-29· IdeaLift

multiple (glob widening)

Widened globs across CRIT-SV-NO-SILENT-PASS, HIGH-SV-METHODOLOGY-VERSIONED, HIGH-SV-EVIDENCE-RETENTION, CRIT-SV-NO-PRE-POPULATED-ATTESTATION, CRIT-SV-AI-REVIEW-GATE, INFO-SV-TRUST-PRINCIPLES-LINK to include monorepo-conventional paths apps/** and packages/**. IdeaLift's apps/web/src/lib/ AI SDK usage was missed by single-package globs. Validated backwards-compatible against FieldLedger and ClarityLift.

v1.5.0

2026-04-29· ClarityLift

HIGH-SV-INTEGRITY-MD-CLAIMS-VERIFIABLE

Added HIGH-SV-INTEGRITY-MD-CLAIMS-VERIFIABLE — documentation drift detection. Two-tier: structural lint (every dated entry must reference a file path, commit, or #N) plus runnable assertions for high-value claim phrasings (link added, marker added, exemption added, Trust Principles) via audits/integrity-claims.json sidecar. Strikethrough text retracted. The framework's own honesty discipline applied to its documentation layer.

v1.4.0

2026-04-28· FieldLedger

CRIT-SV-NO-PRE-POPULATED-ATTESTATION

Revised CRIT-SV-NO-PRE-POPULATED-ATTESTATION from filename-based to co-occurrence (corpus-level content check). Same root cause as v1.3.0: customer-submitted markers live at the persistence/schema layer, not in the library files where attestation output is computed. Filename-based globs miss layered architectures. Both forward-drift directions now caught.

v1.3.0

2026-04-28· FieldLedger

CRIT-SV-AI-REVIEW-GATE

Promoted CRIT-SV-AI-REVIEW-GATE to base as a co-occurrence rule. FieldLedger's per-product filename-based version false-negativated: AI-output review markers (generatedByModel) lived at entity-schemas.ts and the API route, not in cpars-drafting.ts where the rule's globs targeted. Real codebases use layered architectures. Trigger: AI SDK imports / LLM call patterns. Required: review-gate marker anywhere in corpus.

v1.2.0

2026-04-28· FieldLedger

CRIT-SV-NO-BASE-ID-OVERRIDE

Added CRIT-SV-NO-BASE-ID-OVERRIDE meta-rule. Per-product manifests must not re-use base rule ids — closes the silent-loosening drift vector where a product could broaden a base check's globs and the base id would appear enforced when actually relaxed. Products extend with product-specific ids (HIGH-FL-*, CRIT-CL-*, etc.); they never override. Enforced at manifest-merge time.

Discipline maintained

  • Every revision is tied to a real product audit. No speculative additions.
  • Every revision is validated backwards-compatible against the products audited so far.
  • Calibration fixes (regex / glob widening) are minor versions. Structural additions (new rule, new C3 axis, new check kind) are also minor versions until v2.0 — semver-strict rule removals or shape changes will be major.
  • The framework's documentation layer is itself rule-checked (HIGH-SV-INTEGRITY-MD-CLAIMS-VERIFIABLE) so this audit log can't drift from the case studies it points at.

Source: manifests/base-v1.json changelog field. Every entry on this page corresponds 1:1 to a changelog entry there.