📖About

Introduce BUSINESS LINES as a first-class concept (the elevation of what was called a project). Create a new Business Catalogue app owned by Clara, an EXACT clone of the Services Catalogue template, listing business lines. Seed the first and only business: Carolverse, whose main service is enabling the production of new services for new businesses leveraging Carolverse design templates + architectural principles. A business has all the same properties as a service PLUS three differences: (1) its owner is always a HUMAN (Ninad for Carolverse); (2) it has its own dedicated VMs; (3) it has investments and earnings from external users. Update policies, SST, requirements, and Carolopedia with the business-line concept.

⚖️Decisions

• Elrond's bypass methodology checklist (a reminder, not a gate -- you've got this): 0. File it requested_mode='bypass' (planner-vs-bypass is a deliberate choice). bypass_start REFUSES a non-bypass initiative (CAROL-INI-1846), and the dispatcher only skips the bypass lane when the mode says bypass -- a 'planner' mistag lets Merlin's pipeline grab the placeholder step and block your finished work. 1. Filed as planned status -- let the bypass claim/activate it; never file active. 2. Open the bypass (bypass_start) with your droid id + the remediation answer (remediates_initiative_id=NNN, or remediates_nothing=True). 3. Work the blocks for your work-type: template -> design -> code -> test -> review. Do the real work; record decisions on the initiative as you make them. 4. Reality is recorded for you at close -- code (files changed), each decision, and the twin-review verdict become real activities tied to this initiative and show in the Activity Tracker like a planner run (CAROL-INI-1840). No dummy rows. 5. Keep the initiative status moving; it parks in 'reviewing' and is tagged uat-pending for you at close (CAROL-INI-1836), so the stuck-watchdog leaves it alone until UAT. 6. Close runs the gates (design/architecture compliance + caller-audit). If a gate flags something pre-existing or unrelated to your change, waive it with a clear written rationale -- audit, don't skip. 7. Bypass skips the planner's auto-orchestration, NOT the standards. Same template checklist, same review, same observability as a planner run. (elrond)
• A business line is the elevation of the former project concept (ninad)
• Business owner is always human; businesses have dedicated VMs; businesses have external investments+earnings (ninad)
• [status-router] planned -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> closed | event=operator_signoff | Auto-accepted (CAROL-INI-1859): Orion-initiated, >2 days in reviewing with no objection. (el-srac-01)

✅Success criteria

• Business Catalogue app exists, owned by Clara, using the Services Catalogue template (Overview + Architecture tabs) (must_have)
• Carolverse is seeded as the first business with service-equivalent properties + architecture sections (must_have)
• A business owner is always a human (Carolverse owner = Ninad) (must_have)
• Each business shows its dedicated VMs (must_have)
• Each business shows its investments and earnings from external users (must_have)
• Policies, SST, requirements, and Carolopedia are updated with the business-line concept (must_have)