The lifeboat mapping Table's personas row (internal/core/lifeboat/mapping.go, rendered into .abcd/development/brief/00-meta.md) says its Reads are 'personas registry, press-release quote attributions', but the only personas adapter, nativePersonasSource, reads the brief's own personas page (brief/01-product/05-personas.md) through nativeWithBriefFile and nothing else. A reader of the generated table concludes the probe looks for a registry or attributions it never opens. Raised by the ruthless and security reviews of the lane for iss-2610102343100369, which left it outside that remedy.

Frontmatter

.abcd/work/issues/open/iss-2610120820482513-lifeboat-mapping-personas-reads-column.md
open on GitHub ↗ · commit history ↗

mentions1

• iss-2610102343100369Once the drain lane for iss-2610072347247487 lands, the lifeboat probe grounds the personas section from an authored brief file, as it does every other human-owned section. The design record still predicts the old ceiling: the personas row of the lifeboat mapping Table (internal/core/lifeboat mapping.go, around line 151) and the generated mapping table in the brief's 00-meta.md say 'only partial there'. The probe now exceeds that on abcd's own tree, which has about 859 bytes of personas prose. Both of that lane's reviewers noted it as outside its remedy.