Skip to content

Fix stale raiconfig.toml references and an entity_resolution count#94

Open
cafzal wants to merge 1 commit into
mainfrom
fix-raiconfig-yaml-refs
Open

Fix stale raiconfig.toml references and an entity_resolution count#94
cafzal wants to merge 1 commit into
mainfrom
fix-raiconfig-yaml-refs

Conversation

@cafzal

@cafzal cafzal commented Jul 1, 2026

Copy link
Copy Markdown
Collaborator

What

Two small documentation fixes surfaced by the /dev-templates-review pass in #93 (kept out of that PR so it stayed focused on runbooks).

  • raiconfig.tomlraiconfig.yaml across 7 READMEs (bom-reachability, cybersecurity-attack-paths, defect_root_cause, disease-outbreak-prevention, humanitarian-aid-supply-chain, it-dependency-mapping, wildlife-conservation-network). rai init now emits raiconfig.yaml; the .toml name was stale and would send users looking for a file that isn't created.
  • entity_resolution runbook count: the chain summary said the pipeline resolves 51 records into "30 insured parties," but STAGE 1 and the resolve step both report 31 auto-resolved (the 30 true people plus one review-band split held out of the merge). Corrected the summary to 31 so the three references agree.

- raiconfig.toml -> raiconfig.yaml across 7 READMEs (rai init now emits
  raiconfig.yaml; the .toml name was stale).
- entity_resolution runbook: chain summary said the pipeline resolves 51
  records into 30 parties, but STAGE 1 and the resolve step both report 31
  auto-resolved (30 true people plus one review-band split); fix the
  summary to 31 to match.
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