RISK-WP-0001 T01-T06,T08: the four instruments, the index, and the first grading
Severity (impact x likelihood, fidelity modifier for controls that lie,
headline-vs-constraint, build-mode double grade, the floor), disclosure
(publish/embargoed/restricted, and the build-mode deferral re-taken and
narrowed with RISK-F-0001 in hand), escalation (the five INTENT triggers
settled plus an ordering-hazard trigger the RISK-F-0002 case forced;
proposed, awaiting the custodian), review (intervals, what a review is,
what missing one produces, the production re-score).
Then applied: RISK-F-0001 critical/embargoed/escalated, RISK-F-0002
medium with a high constraint on RISK-F-0001's remediation, filed as a
peer and escalated only on the ordering, RISK-F-0003 high/embargoed/no
escalation. No unset field remains.
REGISTER.md is generated; make check reports overdue, stalled, ungraded
and unanswered escalations without changing anything.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-19 23:29:39 +02:00
|
|
|
PY := python3
|
|
|
|
|
TOOLS := tools
|
|
|
|
|
|
2026-09-22 10:19:49 +02:00
|
|
|
# Parameters for the query and write targets (see `make help` for examples).
|
|
|
|
|
ID ?=
|
|
|
|
|
SEV ?=
|
|
|
|
|
SYSTEM ?=
|
|
|
|
|
OUTCOME ?=
|
|
|
|
|
NOTE ?=
|
RISK-WP-0001 T01-T06,T08: the four instruments, the index, and the first grading
Severity (impact x likelihood, fidelity modifier for controls that lie,
headline-vs-constraint, build-mode double grade, the floor), disclosure
(publish/embargoed/restricted, and the build-mode deferral re-taken and
narrowed with RISK-F-0001 in hand), escalation (the five INTENT triggers
settled plus an ordering-hazard trigger the RISK-F-0002 case forced;
proposed, awaiting the custodian), review (intervals, what a review is,
what missing one produces, the production re-score).
Then applied: RISK-F-0001 critical/embargoed/escalated, RISK-F-0002
medium with a high constraint on RISK-F-0001's remediation, filed as a
peer and escalated only on the ordering, RISK-F-0003 high/embargoed/no
escalation. No unset field remains.
REGISTER.md is generated; make check reports overdue, stalled, ungraded
and unanswered escalations without changing anything.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-19 23:29:39 +02:00
|
|
|
|
2026-09-22 10:19:49 +02:00
|
|
|
.DEFAULT_GOAL := help
|
|
|
|
|
.PHONY: help list all show waits escalations policies check due fixes coverage \
|
|
|
|
|
register checked test
|
RISK-WP-0001 T01-T06,T08: the four instruments, the index, and the first grading
Severity (impact x likelihood, fidelity modifier for controls that lie,
headline-vs-constraint, build-mode double grade, the floor), disclosure
(publish/embargoed/restricted, and the build-mode deferral re-taken and
narrowed with RISK-F-0001 in hand), escalation (the five INTENT triggers
settled plus an ordering-hazard trigger the RISK-F-0002 case forced;
proposed, awaiting the custodian), review (intervals, what a review is,
what missing one produces, the production re-score).
Then applied: RISK-F-0001 critical/embargoed/escalated, RISK-F-0002
medium with a high constraint on RISK-F-0001's remediation, filed as a
peer and escalated only on the ordering, RISK-F-0003 high/embargoed/no
escalation. No unset field remains.
REGISTER.md is generated; make check reports overdue, stalled, ungraded
and unanswered escalations without changing anything.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-19 23:29:39 +02:00
|
|
|
|
2026-09-22 10:19:49 +02:00
|
|
|
##@ Inspect the register (read-only)
|
RISK-WP-0001 T01-T06,T08: the four instruments, the index, and the first grading
Severity (impact x likelihood, fidelity modifier for controls that lie,
headline-vs-constraint, build-mode double grade, the floor), disclosure
(publish/embargoed/restricted, and the build-mode deferral re-taken and
narrowed with RISK-F-0001 in hand), escalation (the five INTENT triggers
settled plus an ordering-hazard trigger the RISK-F-0002 case forced;
proposed, awaiting the custodian), review (intervals, what a review is,
what missing one produces, the production re-score).
Then applied: RISK-F-0001 critical/embargoed/escalated, RISK-F-0002
medium with a high constraint on RISK-F-0001's remediation, filed as a
peer and escalated only on the ordering, RISK-F-0003 high/embargoed/no
escalation. No unset field remains.
REGISTER.md is generated; make check reports overdue, stalled, ungraded
and unanswered escalations without changing anything.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-19 23:29:39 +02:00
|
|
|
|
2026-09-22 10:19:49 +02:00
|
|
|
list: ## Live findings, most severe first. Filters: make list SEV=high | make list SYSTEM=qonto-assistant
|
|
|
|
|
@$(PY) $(TOOLS)/risk.py list $(if $(SEV),--severity $(SEV)) $(if $(SYSTEM),--system $(SYSTEM))
|
2026-08-20 08:05:42 +02:00
|
|
|
|
2026-09-22 10:19:49 +02:00
|
|
|
all: ## Every finding, including fixed and withdrawn
|
|
|
|
|
@$(PY) $(TOOLS)/risk.py list --all $(if $(SEV),--severity $(SEV)) $(if $(SYSTEM),--system $(SYSTEM))
|
|
|
|
|
|
|
|
|
|
show: ## One finding or regulatory record: make show ID=RISK-F-0012
|
|
|
|
|
@test -n "$(ID)" || { echo 'usage: make show ID=RISK-F-0012'; exit 2; }
|
|
|
|
|
@$(PY) $(TOOLS)/risk.py show $(ID)
|
|
|
|
|
|
|
|
|
|
waits: ## What the register waits on, or owes, ordered by default date
|
|
|
|
|
@$(PY) $(TOOLS)/risk.py waits
|
RISK-WP-0004: five of six tasks done; the executor is the operator's call
T02 inbox check, wired into make check and verified against the actual
2026-08-19 failure — replayed at that moment it surfaces all three
messages that were already waiting. T03 sweeps the rest of the
quietly-tolerated class: bad dates, cadence off the ladder, undefined
disclosure states, dangling constraint_on and related refs, embargoes
without conditions, escalations without triggers. T04 requests
verification of user-engine's tenant boundary — the first walk down the
on-request path, chosen as a consumer not already known to fail it. T05
established by trying what this register can verify: cluster yes, OpenBao
403. T06 puts regulatory records on the findings ladder.
T01 stays in progress: the procedure, make due and make checked exist,
but arming something that runs them on schedule is a standing compute
commitment and the operator's to make.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-20 08:49:23 +02:00
|
|
|
|
2026-09-22 10:19:49 +02:00
|
|
|
escalations: ## Escalations and their delivery state
|
|
|
|
|
@$(PY) $(TOOLS)/risk.py escalations
|
|
|
|
|
|
|
|
|
|
policies: ## Regulatory records and full legal policies with next review
|
|
|
|
|
@$(PY) $(TOOLS)/risk.py policies
|
|
|
|
|
|
|
|
|
|
##@ Run the register
|
|
|
|
|
|
|
|
|
|
check: ## Full sweep: verify the index, report due and quiet work, read the inbox
|
|
|
|
|
@$(PY) $(TOOLS)/check_all.py
|
|
|
|
|
|
|
|
|
|
due: ## Just the work list: what needs a check right now
|
2026-09-22 07:56:58 +02:00
|
|
|
@$(PY) $(TOOLS)/register_check.py
|
RISK-WP-0004: five of six tasks done; the executor is the operator's call
T02 inbox check, wired into make check and verified against the actual
2026-08-19 failure — replayed at that moment it surfaces all three
messages that were already waiting. T03 sweeps the rest of the
quietly-tolerated class: bad dates, cadence off the ladder, undefined
disclosure states, dangling constraint_on and related refs, embargoes
without conditions, escalations without triggers. T04 requests
verification of user-engine's tenant boundary — the first walk down the
on-request path, chosen as a consumer not already known to fail it. T05
established by trying what this register can verify: cluster yes, OpenBao
403. T06 puts regulatory records on the findings ladder.
T01 stays in progress: the procedure, make due and make checked exist,
but arming something that runs them on schedule is a standing compute
commitment and the operator's to make.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-20 08:49:23 +02:00
|
|
|
@$(PY) $(TOOLS)/inbox_check.py
|
RISK-WP-0005-T01: read the fix records, and two findings moved
fix_tracker.py resolves fix_tracking against the owning repo's workplan
file — the ADR-001 source of truth — and uses the file's last commit date
as the honest answer to 'has this moved', independent of whether the
register looked. Archived workplans are searched too, so a finished fix
that was filed away does not read as missing.
First run, three findings it should have known about:
RISK-F-0005 — AUDIT-WP-0008-T04 has read done since 2026-08-18. The fix
this finding asked for has landed and the register spent three days not
knowing. Now mitigated, embargo lifted, disclosure public. Not fixed:
that needs a probe, and T05's adversarial evidence artifact still reads
wait.
RISK-F-0002 — both tracked records were closed before the finding was
filed: WARDEN-WP-0007 archived 2026-07-08, FLEX-WP-0007 finished
2026-06-29, against a finding of 2026-08-18 that names FLEX-WP-0007 as
the blocker. Routed as a question, not a conclusion.
Four findings carry no fix tracking at all, which the report now says out
loud rather than leaving as an empty field.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-21 08:29:38 +02:00
|
|
|
|
2026-09-22 10:19:49 +02:00
|
|
|
fixes: ## State of every fix the register tracks, read from owner workplans
|
RISK-WP-0005-T01: read the fix records, and two findings moved
fix_tracker.py resolves fix_tracking against the owning repo's workplan
file — the ADR-001 source of truth — and uses the file's last commit date
as the honest answer to 'has this moved', independent of whether the
register looked. Archived workplans are searched too, so a finished fix
that was filed away does not read as missing.
First run, three findings it should have known about:
RISK-F-0005 — AUDIT-WP-0008-T04 has read done since 2026-08-18. The fix
this finding asked for has landed and the register spent three days not
knowing. Now mitigated, embargo lifted, disclosure public. Not fixed:
that needs a probe, and T05's adversarial evidence artifact still reads
wait.
RISK-F-0002 — both tracked records were closed before the finding was
filed: WARDEN-WP-0007 archived 2026-07-08, FLEX-WP-0007 finished
2026-06-29, against a finding of 2026-08-18 that names FLEX-WP-0007 as
the blocker. Routed as a question, not a conclusion.
Four findings carry no fix tracking at all, which the report now says out
loud rather than leaving as an empty field.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-21 08:29:38 +02:00
|
|
|
@$(PY) $(TOOLS)/fix_tracker.py
|
2026-08-21 08:34:30 +02:00
|
|
|
|
2026-09-22 10:19:49 +02:00
|
|
|
coverage: ## Which estate repos the register has never heard from
|
2026-08-21 08:34:30 +02:00
|
|
|
@$(PY) $(TOOLS)/coverage.py
|
2026-09-22 07:56:58 +02:00
|
|
|
|
2026-09-22 10:19:49 +02:00
|
|
|
##@ Record and maintain
|
|
|
|
|
|
|
|
|
|
checked: ## Record a check: make checked ID=RISK-F-0012 OUTCOME=clean|moved NOTE="what was seen"
|
|
|
|
|
@if [ -n "$(ARGS)" ]; then $(PY) $(TOOLS)/record_check.py $(ARGS); \
|
|
|
|
|
else test -n "$(ID)" -a -n "$(OUTCOME)" || { echo 'usage: make checked ID=RISK-F-0012 OUTCOME=clean NOTE="..."'; exit 2; }; \
|
|
|
|
|
$(PY) $(TOOLS)/record_check.py $(ID) $(OUTCOME) $(if $(NOTE),"$(NOTE)"); fi
|
|
|
|
|
@$(PY) $(TOOLS)/register_index.py
|
|
|
|
|
|
|
|
|
|
register: ## Rebuild REGISTER.md from findings/
|
|
|
|
|
@$(PY) $(TOOLS)/register_index.py
|
|
|
|
|
|
|
|
|
|
test: ## Run the tool test suite
|
2026-09-22 07:56:58 +02:00
|
|
|
@PYTHONDONTWRITEBYTECODE=1 $(PY) -m unittest discover -s tests -v
|
2026-09-22 10:19:49 +02:00
|
|
|
|
|
|
|
|
##@ Help
|
|
|
|
|
|
|
|
|
|
help: ## List targets with examples (the default)
|
|
|
|
|
@awk 'BEGIN {FS = ":.*## "} \
|
|
|
|
|
/^##@/ {printf "\n\033[1m%s\033[0m\n", substr($$0, 5); next} \
|
|
|
|
|
/^[a-z][a-zA-Z_-]*:.*## / {printf " \033[36m%-12s\033[0m %s\n", $$1, $$2}' $(MAKEFILE_LIST)
|
|
|
|
|
@echo
|
2026-09-22 10:26:00 +02:00
|
|
|
@echo "Defer a check (founder decision): make checked ARGS='RISK-F-0012 defer 2026-10-15 \"reason\"'"
|