Skip to content

docs(q-and-a): add 12 Kognitos-point cross-references#5

Open
smuchow1962 wants to merge 1 commit into
mainfrom
docs/kognitos-12pt-cross-reference
Open

docs(q-and-a): add 12 Kognitos-point cross-references#5
smuchow1962 wants to merge 1 commit into
mainfrom
docs/kognitos-12pt-cross-reference

Conversation

@smuchow1962
Copy link
Copy Markdown
Collaborator

Summary

Apply 14 operations from the 2026-05-20 Kognitos 12-point audit cycle to docs/q-and-a.md. Tag format is (kognitos point N) — lowercase, integer N, single space separators, end of Answer cell.

  • 5 tag-adds to existing rows (Points 8, 11×2, 12×2)
  • 9 new rows covering Points 1, 2, 3 (Variant A), 4, 5, 6, 7, 8 (epistemic scope), 9, 10 (Variant A)

Placement follows Option A — distributed by theme to preserve the role-affinity scan. No introductory paragraph about Kognitos per Steve's directive (the parentheticals stand on their own). Boundary-of-the-claim discipline is baked into every drafted cell (institution-side dependencies, epistemic scope, temporal scope named where applicable).

The Point 12 lead-row tag-add also carries Rosanne's tail-sentence pointing at §10.53 / §10.54 / §4.1.3 so a post-quantum-aware reader doesn't read the present-tense integrity claim as time-invariant.

Theme placement

Point Theme
1 Implementation and operations
2 Implementation and operations
3 (A) Audit committee and board governance
4 Model risk management and regulatory mapping
5 Model risk management and regulatory mapping
6 Model risk management and regulatory mapping
7 Cryptographic discipline and standards
8 (epistemic scope) Privacy and data-subject rights
9 Tamper detection and independent verification
10 (A) Legal evidentiary posture and litigation

Variant B follow-on

Points 3 and 10 ship Variant A today. Variant B follows after PRD-3 lands the Seam D audit.actor.* family and the audit.downstream_action.* family.

Downstream

The herald-website auto-mirrors docs/q-and-a.md into web/src/content/mrm-spec/docs/q-and-a.md via web/scripts/sync-mrm-spec.cjs. The /mrm/docs/q-and-a page picks up the new rows at the next build. No additional website work needed — Dawn confirmed in her dispatch.

Source of record

All cell text was lifted verbatim from the consolidated pack:
E:\dev\MMP.Media\_assistant_drafts\wiki\market-research\2026-05-20-CONSOLIDATED-kognitos-qa-pack-for-steve.md (the "14 operations" section)

That pack composed work from Pearl (12-field schema), Richard (coverage audit), Rosanne (seam inventory + falsification cross-check), and Laura (CHANGELOG narrative for the 4 separate spec changes).

Test plan

  • docs/q-and-a.md renders cleanly in GitHub's markdown preview (no broken table rows)
  • All 12 Kognitos points are grep-findable as (kognitos point N) (currently: 15 instances across 14 operations; Point 8 appears twice by design — once tag-add, once new row)
  • After merge, the herald-website npm run sync-mrm-spec + build picks up the new rows
  • The role-affinity filter on /mrm/docs/q-and-a still works against the new rows (their audience icons compose with the existing role-filter toolbar)

… new rows)

Apply 14 operations from the 2026-05-20 Kognitos 12-point audit cycle.
Tag format: (kognitos point N) — lowercase, integer N, end of Answer cell.

Tag-adds (5) to existing rows:
- Point 8 — line 213 (Consumer access: adverse-action principal reasons)
- Point 11 — line 187 (Privacy: Article 22)
- Point 11 — line 294 (Vendor management: human-override path)
- Point 12 — line 38 (Tamper-detection lead row) + Rosanne tail-sentence
  pointing at §10.53/§10.54/§4.1.3 so a post-quantum-aware reader doesn't
  read the present-tense integrity claim as time-invariant
- Point 12 — line 46 (Tamper-detection: opposing-counsel attack row)

New rows (9), Variant A for Points 3 and 10:
- Point 1 — NTP-synced UTC timestamp → Implementation theme
- Point 2 — Unique decision ID → Implementation theme
- Point 3 (Variant A) — Authenticated human user identity → Audit committee
- Point 4 — AI system identity and version → MRM theme
- Point 5 — Model identity and version → MRM theme
- Point 6 — Inputs received with source attribution → MRM theme
- Point 7 — Specific policy / rule / prompt invoked → Crypto discipline theme
- Point 8 — Hash-vs-plaintext epistemic scope → Privacy theme
- Point 9 — Output produced (stream-finish binding) → Tamper-detection theme
- Point 10 (Variant A) — Action in downstream systems → Legal evidentiary

Placement: Option A (distributed by theme), preserving role-affinity scan.
No introductory paragraph about Kognitos per Steve's directive.
Boundary-of-the-claim discipline baked into every drafted cell.

Variant B for Points 3 and 10 follows after PRD-3 lands Seam D (audit.actor.*)
and the audit.downstream_action.* family.

Source-of-record for the operations:
E:/dev/MMP.Media/_assistant_drafts/wiki/market-research/
2026-05-20-CONSOLIDATED-kognitos-qa-pack-for-steve.md

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant