📖About

Two sections in apps/requirements/technical_requirements.md frame Carol's requirements in terms of BB ('Modular Design Parity (Superset of BB)' references BB twice; 'BB as Blueprint' tells Carol to use BB patterns as the starting point). Per Ninad 2026-05-01: 'Carol can exist independently without BB. The requirements should focus on functionality, not parity.' Rewrite both sections in Carol-functional terms. Delete BB-as-Blueprint section. Move any genuinely architectural content to designs.db.

⚖️Decisions

• Carol's requirements are functional — they describe what Carol must do, not what Carol must look like compared to BB. All BB references removed from technical_requirements.md. — User locked: 'There should not be any reference of BB in carol requirements, as carol can exist independently without BB. The requirements should focus on functionality, not parity.' (Ninad)
• 'Modular Design Parity (Superset of BB)' renamed to 'Modular Design — Shared Module Architecture' with content rewritten in functional terms (each module provides a defined cross-cutting capability). — The architectural rule (single shared/, defined interfaces, no app-to-app imports) is the value. The 'parity with BB' framing is incidental. (Orion)
• 'BB as Blueprint' section deleted. Any genuinely architectural content moved to designs.db; nothing about copying-BB belongs in Carol's requirements. — BB-as-Blueprint is not a Carol requirement; it's a process suggestion that doesn't belong in a SST. (Orion)
• requester rewritten ninad -> orion per CAROL-INI-744: orion is the only human-CLI requester — Backfill of historical rows after INI744 added API-level refusal of requester=ninad. Orion is Ninads CLI agent; all human-originated initiatives are filed with requester=orion. (orion)

✅Success criteria

• grep -ciE '\\bbb\\b|big brother' technical_requirements.md returns 0. (must_have)
• /api/technical returns the rewritten Modular Design section with all 8 shared modules listed and interface rules preserved. (must_have)
• /api/technical does NOT return a 'BB as Blueprint' section. (must_have)
• Visual on /dev/requirements/ Technical tab: rewritten section appears, no BB-blueprint section. (must_have)
• Regression diff vs prior run: 0 NEW FAILURE. (must_have)