Origin
IdeaLift TIF audit, 2026-04-29. Matrix: Startvest-LLC/idealift audits/tif-compliance.md § Documentation drift.
The pattern
IdeaLift's INTEGRITY.md ## Outstanding Risks / Known Gaps (last updated 2026-04-25) carried this line:
"No public link from IdeaLift marketing → Startvest Trust Principles. Add to footer once Trust Principles page is published at startvest.ai."
The 2026-04-29 audit found the link IS present at apps/web/src/app/privacy/page.tsx:241. Reverse documentation drift — claim of absence when the resource exists. ClarityLift's drift was forward (claim of presence; actually absent). IdeaLift's was reverse. Same silent-pass pattern at the documentation layer; different direction.
The new HIGH-SV-INTEGRITY-MD-CLAIMS-VERIFIABLE rule (base v1.5.0) currently scans only the ## Recent Changes section. The IdeaLift drift was in ## Outstanding Risks / Known Gaps — out of scope.
Proposed extension
Extend the rule's scope (configurable per recentChangesHeading) to support multiple sections, with potentially different policies per section:
Recent Changes — current behavior (structural lint + high-value claim assertions)Outstanding Risks / Known Gaps — additional claim type: gap claims must remain true. If a gap entry says "X is missing" or "X not yet operational", the rule could verify against a sidecar assertion that X is indeed missing.
This would catch reverse drift (claim of absence; actually present) the same way the current rule catches forward drift.
Implementation note
The integrity-md-claims check kind in src/runner.mjs already supports recentChangesHeading as a configurable field. Extending it to accept a list of section names + per-section policy is straightforward.
Acceptance criteria
Priority rationale
P2: not blocking. Same logic as #5 — drift accumulates over time, and the audit pattern is now well-established. Worth picking up before audit 4 (HirePosture) to maximize the catch rate.
Origin
IdeaLift TIF audit, 2026-04-29. Matrix: Startvest-LLC/idealift audits/tif-compliance.md § Documentation drift.
The pattern
IdeaLift's INTEGRITY.md
## Outstanding Risks / Known Gaps(last updated 2026-04-25) carried this line:The 2026-04-29 audit found the link IS present at
apps/web/src/app/privacy/page.tsx:241. Reverse documentation drift — claim of absence when the resource exists. ClarityLift's drift was forward (claim of presence; actually absent). IdeaLift's was reverse. Same silent-pass pattern at the documentation layer; different direction.The new
HIGH-SV-INTEGRITY-MD-CLAIMS-VERIFIABLErule (base v1.5.0) currently scans only the## Recent Changessection. The IdeaLift drift was in## Outstanding Risks / Known Gaps— out of scope.Proposed extension
Extend the rule's scope (configurable per
recentChangesHeading) to support multiple sections, with potentially different policies per section:Recent Changes— current behavior (structural lint + high-value claim assertions)Outstanding Risks / Known Gaps— additional claim type: gap claims must remain true. If a gap entry says "X is missing" or "X not yet operational", the rule could verify against a sidecar assertion that X is indeed missing.This would catch reverse drift (claim of absence; actually present) the same way the current rule catches forward drift.
Implementation note
The
integrity-md-claimscheck kind insrc/runner.mjsalready supportsrecentChangesHeadingas a configurable field. Extending it to accept a list of section names + per-section policy is straightforward.Acceptance criteria
dev-tools/integrity-md-claims-format.mdPriority rationale
P2: not blocking. Same logic as #5 — drift accumulates over time, and the audit pattern is now well-established. Worth picking up before audit 4 (HirePosture) to maximize the catch rate.