Carolopedia

A public encyclopedia of Carolverse.

๐Ÿ“– Carolopedia โ€บ Guides โ€บ Reference dataGuide page

Reference data

๐Ÿ“–What an access request asks for

Guest access (the open access: Carol's and Sam's chats) or a service subscription such as Blueprint; the two are separate approvals. Service: Operations. Kept by Jarvis.

- guest_access: Guest access: Carol's and Sam's chats, while the temporary guest gate stands; no subscription
- subscription: A service subscription such as Blueprint, recommended by the agent the project's rules name and approved by an estate operator

๐Ÿ“–Agent deployment status

Whether an agent holds a post. NOT the same question as agents.status (active / retired), which answers whether the agent still exists: a benched agent is active, it simply holds no post yet. Service: Agent and Human Resources. Kept by Athena.

- bench: Created and not yet deployed to a post. While here the agent reports to the head of Agent Resources.
- deployed: Holds the post prescribed for it and reports to the line prescribed for it.

Allowed moves: bench to deployed, deployed to bench.

๐Ÿ“–Agent onboarding bench-only asker

The askers Athena's door holds to BENCH requests: a request from one of them must ask for a bench agent (designation bench, the estate's own project, reporting to the onboarding track's owner). The door reads this record live and the registry refuses their other requests at the write seam. Values are agent ids. Service: Agent and Human Resources. Kept by Athena.

- agt_005: Athena (Head of Agent and Human Resources) may ask Athena's door for a BENCH agent only, to keep the bench close to ten (Rulings Repo agent-resources #989, #988).

๐Ÿ“–Athena's name book

The names Athena gives bench agents (agent-resources #986), taken in order, each used once. Kept by Athena. Service: Agent and Human Resources. Kept by Athena.

- Apollo: Proposed by Athena with her own model for a bench agent, 2026-11-18
- Artemis: Proposed by Athena with her own model for a bench agent, 2026-11-18
- Freya: Proposed by Athena with her own model for a bench agent, 2026-11-18
- Frigg: Proposed by Athena with her own model for a bench agent, 2026-11-18
- Baldur: Proposed by Athena with her own model for a bench agent, 2026-11-18
- Hera: Proposed by Athena with her own model for a bench agent, 2026-11-18
- Hermes: Proposed by Athena with her own model for a bench agent, 2026-11-18
- Hestia: Proposed by Athena with her own model for a bench agent, 2026-11-18
- Perseus: Proposed by Athena with her own model for a bench agent, 2026-11-18
- Theseus: Proposed by Athena with her own model for a bench agent, 2026-11-18

๐Ÿ“–Agent bench rest days

How many days a declined or refused bench request holds its place, so Athena does not ask again at once. Service: Agent and Human Resources. Kept by Athena.

- 7: A declined or refused bench request holds its place for seven days.

๐Ÿ“–Agent bench subscription

The one provider:model pair a bench agent is asked for with; its deployment re-chooses it. Service: Agent and Human Resources. Kept by Athena.

- claude:claude-opus-5: A bench agent is asked for on Claude Opus 5; its deployment re-chooses it.

๐Ÿ“–Agent bench target

How many agents Athena keeps on the bench; she asks for the shortfall on every run (agent-resources #988). Service: Agent and Human Resources. Kept by Athena.

- 10: Athena keeps the bench close to ten agents (agent-resources #988).

๐Ÿ“–Project statuses a new-agent request may name

The values of project.status for which Athena's onboarding door accepts a request naming that project. Approved: the administrator has approved the project, so its agents may be asked for before it goes live. Active: the project is live. A requested or retired project is refused by name. Service: Agent and Human Resources. Kept by Athena.

- approved: The project's administrator approved it; its agents may be asked for before it goes live.
- active: The project is live.

๐Ÿ“–Agent onboarding mandatory detail

The details a request for a new agent must carry before an agent is created from it. The onboarding door reads this record live: adding a detail is a change here, never a change to code. Service: Agent and Human Resources. Kept by Athena.

- name: The agent's name; no two agents share one.
- purpose: What the agent is for.
- project: The project the agent is deployed to.
- reports_to: The agent it reports to once deployed.
- department: Its department, housed in a realm so the agent has an address.
- level (retired): Its level in the organisation.
- service: The service it belongs to.
- subscription: The provider and model it runs on, prescribed by the requester.
- designation: The new agent's designation in its project, as root's list of approved agents holds it; written as the agent's title.
- role: The new agent's role, as root's list of approved agents holds it: a text, items separated by ';', or a list of texts.
- responsibilities: The new agent's responsibilities, as root's list of approved agents holds them: a text, items separated by ';', or a list of texts.

๐Ÿ“–Agent onboarding permitted asker

The agents Athena accepts a request for a new agent from. The onboarding door reads this record live and the registry refuses any other asker at the write seam. Values are agent ids. Service: Agent and Human Resources. Kept by Athena.

- agt_034: Leo (Head of Strategy) may ask Athena for a new agent.
- agt_023: Orion (Deputy Chairman) may ask Athena for a new agent.
- agt_005: Athena (Head of Agent and Human Resources) may ask Athena's door for a BENCH agent only, to keep the bench close to ten (Rulings Repo agent-resources #989, #988).

๐Ÿ“–Agent onboarding request status

Where a request for a new agent stands on its one route. Service: Agent and Human Resources. Kept by Athena.

- requested: Complete; waiting for the administrator's decision.
- refused: Incomplete or invalid when it was made; the faults are named on the request. No agent can come of it.
- approved: The administrator approved it; the agent's id is reserved.
- declined: The administrator declined it, with the reason.
- created: The agent exists, on the bench.
- build_filed: The rest of the agent's build is filed for the asker.
- deployed: The asker accepted; the agent holds its post.

Allowed moves: approved to created, build_filed to deployed, created to build_filed, requested to approved, requested to declined.

๐Ÿ“–Albus's preferred subjects

The arcs and pursuits whose work Albus's lane puts above every other initiative, arc and pursuit, on top of the common prioritisation (#655): every member of a named arc and every step of a named pursuit is architecture compliance work for his lane. Albus owns it; the add-on preference changes his lane's pick order only. Service: Build Initiatives. Kept by Albus.

- CAROL-ARC-0026: Architecture compliance (Themis's audit arc): bring the platform to zero unwaived architecture violations and keep it there; its members are architecture compliance work Albus's lane puts first (#655).

๐Ÿ“–App access policy (agents)

Which agents may read an app. One of the two audiences ruled by; the human audience is app.access_policy_humans. The gate fails CLOSED, so a value outside this vocabulary refuses every agent except the owner. Service: System Services. Kept by Radagast.

- public: Every agent without restriction โ€” the widest agent class.
- global: Every agent may read the app.
- default: The owner agent and their supervisors; the reporting line IS the containment (P.01.03.05.09).
- classified: Every agent may enter but sees ONLY ITS OWN data; the app scopes every row to the requesting identity.
- limited: Named agents only โ€” the explicit mapping on the app record (named_agents) IS the naming.
- confidential: The owner agent and the operator only; every other agent is refused.

๐Ÿ“–App access policy (humans)

Which humans may open an app. One of the two audiences ruled by; the agent audience is app.access_policy. The gate fails CLOSED through the subscription chain. Service: System Services. Kept by Radagast.

- public: All humans โ€” no login required.
- global: Any signed-in user, irrespective of subscription.
- default: Signed-in users whose PROJECT subscribes to the service this app belongs to.
- classified: Signed-in subscribed users, each seeing only their own data; the app scopes every row to the requesting identity.
- limited: Signed-in subscribed users NAMED on the app record (named_users) only.
- confidential: Project admin plus the carolverse admin only.

๐Ÿ“–App run mode

Whether an app runs all the time or starts on demand and stops when idle. Service: System Services. Kept by Radagast.

- always_on: Runs all the time. The caretaker revives it if it falls over. The default: every app was always-on before, and the public and critical apps stay so.
- on_demand: Starts on its first request and stops after a stated idle time; its port is held by a listener while it sleeps, so a visit always reaches it. Checkers read the sleeping app's listener and never wake it (Rulings Repo system-services #1117).

๐Ÿ“–App status

The lifecycle state of one APP โ€” a surface somebody opens. NOT the status of the service the app belongs to: a service is a business capability with money and tracks behind it, and a LIVE service can hold a DECOMMISSIONED app. That is exactly what happened when the Communications app folded into User Engagement while the Communications service carried on unchanged. Two of these values are OBSERVED (active, inactive: is anyone using it) and two are DECIDED (paused, decommissioned: do we want it running). The automated restart refuses only the decided pair. Service: System Services. Kept by Radagast.

- active: In regular use. The caretaker revives it if it falls over.
- inactive: Nobody has used it for a long time. This is an OBSERVATION, not a decision โ€” and deliberately not a kill switch: a rarely-used but needed app (an emergency tool, a yearly report) is still revived if it falls over. Gating the restart on 'active' alone would let such an app die quietly and stay dead until somebody needed it.
- paused: Deliberately stopped for now, and expected back. The caretaker does not revive it and a restart request is refused by name. Reviving it is a decision somebody makes, not something that just happens.
- decommissioned: Deliberately retired โ€” no longer needed. The caretaker never revives it, its route is not rendered, and the record STAYS so the estate can still say what the app was called, which port it held and which user it ran as. Retire, never delete: deleting the record is what once left a retired app's process running with nothing able to stop it.

Allowed moves: active to decommissioned, active to inactive, active to paused, decommissioned to active, inactive to active, inactive to decommissioned, inactive to paused, paused to active, paused to decommissioned.

๐Ÿ“–Arc status

What state a whole arc of work is in. Service: Build Initiatives. Kept by Orion.

- planned: Filed and not started: no member initiative has been worked yet.
- active: Being built: at least one member is executing, or work has begun and is unfinished.
- paused: Deliberately stopped by a decision, and expected to resume. Not a failure.
- completed: Every member has reached a terminal state and the arc's goal is met.
- abandoned: Stopped for good. Kept as history, never deleted.
- split: Closed because its open work moved to right-sized arcs it names; it keeps its finished members.

Allowed moves: active to abandoned, active to completed, active to paused, active to split, completed to active, paused to abandoned, paused to active, paused to split, planned to abandoned, planned to active, planned to paused, planned to split.

๐Ÿ“–Kind of artifact an app holds

What a holding in Heimdall's record is: a store (a database file), a file, or a record (an entry or a table a store holds). Service: Security. Kept by Heimdall.

- store: A database file an app holds
- file: Any other file an app holds
- record: One entry, or one table, an app's store holds

๐Ÿ“–Where an unowned store is placed

The placement the population check gives every UNOWNED store: by the service of the code that names it (shared machinery, design 709 v1.6). Service: Security. Kept by Heimdall.

- placed: the code naming the store that a record places is all one service's: that service holds it (a file no record places is named beside it)
- several: code of two or more services names the store: those services agree on one holding (a file no record places is named beside it)
- unplaced: no code file naming the store is placed by a record: the files are named
- no_code: no code file names the store: a retirement question for Hagrid's retention record, never a holding

๐Ÿ“–Audit finding closure reason

Why a Themis audit finding was closed. A closure made before reasons were recorded has none and reads 'reason unknown' - never backfilled. Service: Audit & Compliance. Kept by Themis.

- fixed_on_rescan: The same check re-ran on the same artifact and found it clean.
- rebuttal_accepted: Themis dismissed the finding on the owner's written rebuttal.
- artifact_retired: The artifact the finding is about no longer exists.
- clean_scan_record: Not a finding: a dated record, born closed, that a scan ran clean.
- waived: A recorded architecture waiver now covers the finding; it is not fixed.
- check_retired: The check that raised the finding was retired in place; the rule it enforced lives on in the one checker, which raises its own finding when the violation still stands.

๐Ÿ“–Ways a client may pay

The ways a Blueprint client may pay an invoice. Each way names the one reader of its evidence in shared.project_billing.PAYMENT_EVIDENCE; Midas marks an invoice paid only from that evidence. Service: Cost Center. Kept by Midas.

- bank_transfer: Paid by bank transfer: evidenced only by matching outgoing lines on the project's own bank statement (shared.project_account_reading.matches, cost-center #447); the standard payment terms name it (cost-center #795).

๐Ÿ“–Company registration status

Where the company's one registration record stands: in formation until the registration completes with its evidence. Service: Leadership. Kept by Clara.

- in_formation: The company is being formed: every document names it as in formation and says who signs for it (leadership #250, #330).
- registered: The registration has completed and its evidence is on the record: documents name the registered company from it.

Allowed moves: in_formation to registered.

๐Ÿ“–Competency grade

The grade a competency holds on a day, judged from real attempts. Service: Agent and Human Resources. Kept by Athena.

- fluent: Does this reliably and often: enough counted attempts in the window and nearly all of them succeeded.
- proficient: Does this reliably: several counted attempts in the window and most of them succeeded.
- learning: Has attempted this, and is not yet reliable at it.
- forgotten: Could do this once, and no longer can: it can no longer run, or its most recent counted attempts all failed after an earlier success.
- ungraded: No counted attempt is on record yet. An unmeasured competency is never called learning.

๐Ÿ“–Compliance obligation applicability

Whether an obligation in Themis's compliance register applies to Denken Labs. Service: Audit & Compliance. Kept by Themis.

- applies: It applies now; the row says why.
- conditional: It applies only when the named condition holds, such as the company being registered in a given country.
- does_not_apply: It does not apply; the row says why, and it is kept so the judgement can be revisited.
- to_be_judged: Not yet judged; a person or Themis must decide, and it is never read as not applying.

๐Ÿ“–Compliance obligation kind

What kind of obligation a row of Themis's compliance register is. Service: Audit & Compliance. Kept by Themis.

- law: A law or regulation that applies, or may apply, to Denken Labs and its estate.
- provider_terms: A governing document of an AI provider for a plan or account the estate actually holds: its terms, usage policy or privacy and data-use terms.
- own_policy: A policy Denken Labs itself publishes, such as its privacy policy.
- committed_policy: An outside policy Denken Labs has publicly committed to keep, such as the Google API Services User Data Policy named in its privacy policy.

๐Ÿ“–Contract cost basis

The contract cost basis, a governed vocabulary of the contract register. Service: Cost Center. Kept by Marco.

- estimate: The amount is the roadmap's estimate, stated as an expectation and never a price: the client is billed as the contract's payment terms say.
- per_hour: The amount is paid for each hour worked, up to the contract's hours cap a day.
- per_day: The amount is paid for each day worked.
- per_month: The amount is paid for each calendar month of the term.
- fixed: The amount is paid once for the whole contract.

๐Ÿ“–Contract kind

The contract kind, a governed vocabulary of the contract register. Service: Cost Center. Kept by Marco.

- internship: An internship with the company for a fixed term, ending with a certificate.
- contractor: An independent contractor's agreement: services for a fee, own taxes, no employment.
- employment: An employment contract.
- vendor: A contract with a vendor the company buys from.
- service: A contract for a service the company provides to a client.

๐Ÿ“–Contract party kind

The contract party kind, a governed vocabulary of the contract register. Service: Cost Center. Kept by Marco.

- person: A person on the registry's persons record (party_ref = the person's id).
- user: a user of a project, as the project records them (users.id) -- the client person a service contract names
- operator: An operator on root's operator list (party_ref = the operator's login).
- vendor: A vendor on Marco's subscription register (party_ref = the subscription key).

๐Ÿ“–Contract pricing model

The contract pricing model, a governed vocabulary of the contract register. Service: Cost Center. Kept by Marco.

- tokens_plus_margin_pay_as_you_go: Tokens plus margin, pay as you go: each month the Client pays for the tokens its work consumed, plus the Company's margin.
- tokens_plus_margin_fixed_subscription: Tokens plus margin, fixed subscription: the Client pays a fixed monthly fee that includes an agreed amount of work; work beyond it is charged as the tokens it consumed, plus the Company's margin.
- price_for_scope: Price for scope: the Client pays the price agreed for the scope this agreement sets out.
- price_for_value: Price for value: the Client pays the price agreed for the value the work delivers.

๐Ÿ“–Contract status

The contract status, a governed vocabulary of the contract register. Service: Cost Center. Kept by Marco.

- draft: Being prepared; not sent to the party.
- sent: Sent to the party for signature.
- signed: Signed by both parties; not yet started.
- active: In force: the term has started.
- ended: The term ended as agreed.
- terminated: Ended before its term, or withdrawn before signature.

Allowed moves: active to ended, active to terminated, draft to sent, draft to signed, draft to terminated, sent to draft, sent to signed, sent to terminated, signed to active, signed to terminated.

๐Ÿ“–Contract notice kind

The contract notice kind, a governed vocabulary of the contract register. Service: Cost Center. Kept by Marco.

- end_ahead: The end watch raised the contract's end ahead of time.
- certificate_due: The end watch raised that an internship's certificate is due at its end.
- certificate_held: The end watch could not issue an internship's certificate at its end, and said why.

๐Ÿ“–Contract template kind

The contract template kind, a governed vocabulary of the contract register. Service: Cost Center. Kept by Marco.

- internship: Template for an internship agreement.
- contractor: Template for an independent contractor agreement.
- employment: Template for an employment contract.
- vendor: Template for a vendor contract.
- service: Template for a service contract with a client.
- internship_certificate: Template for the certificate an internship ends with.

๐Ÿ“–Contract template lawyer review

The contract template lawyer review, a governed vocabulary of the contract register. Service: Cost Center. Kept by Marco.

- not_reviewed: Not for use: no qualified lawyer in its country has reviewed it.
- reviewed: Reviewed by a qualified lawyer in its country; may be used.
- superseded: Replaced by a later version of the template.

๐Ÿ“–CRM application status

Status of an outreach thread. The two values the Glover source used, plus the two lifecycle ends a thread can reach. Service: Sales. Kept by Aurora.

- sent: Outreach sent, no reply yet
- follow-up drafted: A follow-up is drafted, not yet sent
- replied: The lead answered
- closed: Thread closed โ€” outcome in notes

๐Ÿ“–CRM contact stage

Where a person at a lead stands. A customer is a contact at the customer stage โ€” one home for people in the CRM. Service: Sales. Kept by Aurora.

- contact: A person at a lead, not yet a customer
- customer: A key contact at a lead who is a customer

๐Ÿ“–CRM engagement status

Status of an active conversation with a lead (written by Carol's log_engagement). Service: Sales. Kept by Aurora.

- active: Conversation live
- paused: Parked by either side
- closed: Conversation ended โ€” outcome in notes

๐Ÿ“–CRM pipeline

Which CRM deployment a record belongs to. One deployment per pipeline of the shared CRM codebase. Service: Sales. Kept by Aurora.

- sales: Sales pipeline โ€” customers, owned by Aurora, worked by Carol
- partnerships: Partnerships pipeline โ€” research institutes, owned by Aurora, worked by Carol
- investments: Investments pipeline โ€” investors and funding, Clara's Finance track
- research: Research directory โ€” institutes and sources, owned by Obi-Wan

๐Ÿ“–CRM record status

Whether a lead or contact is live. Records retire, never delete. Service: Sales. Kept by Aurora.

- active: Live record
- retired: Retired in place โ€” kept for history, not worked

๐Ÿ“–Kind of customer

Which kind of customer Leo is serving: a self-serve client, a prospect in Sandbox or a client project. Leo's service list is kept separately for each. Service: Blueprint. Kept by Leo.

- self-serve: A customer who signs up and pays for Carolverse's chats on their own, without a project built for them.
- prospect: A business onboarded in Sandbox before it signs a contract: its proof of concept is built and its services run there.
- project: A client whose contract is signed: its project runs on its own estate kernel.

๐Ÿ“–What a dependency holds of the initiative that waits

what a dependency holds of the initiative that waits Service: Build Initiatives. Kept by Elrond.

- start: On start: the waiting initiative cannot start until the prerequisite is met.
- end: To end: the waiting initiative may start, but cannot close until the prerequisite is met.

๐Ÿ“–What a dependency's end may be

what a dependency's end may be Service: Build Initiatives. Kept by Elrond.

- initiative: An initiative family, named CAROL-INI-NNNN.
- pursuit: A pursuit, named CAROL-PUR-NNNN.
- arc: An arc, named CAROL-ARC-NNNN.
- root_step
- answer: An operator's answer, named by the operator communication that asks it; done when that communication is closed, addressed or declined.
- workstation: A step on an operator's computer, named by the person and the release it brings or a moment; done when root's newest workstation report from them names that release or later, or was made at or after that moment.
- release: An operator template release, named vN; done once it is published.
- time: A date and time in UTC; done once it has passed.
- decision: The decision an initiative parked for its filer or for a ruling waits on, named by that initiative; done once the family moves out of parked after that park.

๐Ÿ“–Whether a dependency stands

whether a dependency stands Service: Build Initiatives. Kept by Elrond.

- standing: Filed and not withdrawn: the dependent waits on the prerequisite until it is met.
- withdrawn: Taken back with its reason; kept as history, never deleted.

๐Ÿ“–Email grant purposes

What a person's grant of read-only access to their own mailbox is FOR. Each purpose is its own grant and its own token in the person's folder, so a token granted for one purpose is never read for another. Service: Communications. Kept by Carol.

- enrichment: Carol learns about you from your email: user enrichment (P.05.03.01.03). The original grant; its token keeps its first file name.
- receipts: The company's subscription receipts and credit purchases are read once a day from the administrator's work mailbox for its accounts (Rulings Repo cost-center #279).
- operator-mail: An operator's own work mailbox and calendar, granted by that operator for their own view and their own Orion's reminders and drafts: mail read, mail compose (Google gives drafting only with sending; the estate only drafts) and calendar events read; used only by that operator's own sessions.
- carol-mailbox: Carol's own mailbox, issued again by her own consent: mail read and mail compose, the sign-in kept by Carol's Mail Door alone in her own folder, and the sign-in it replaces revoked at Google.

๐Ÿ“–Escalation category

What kind of thing an escalation is, declared by whoever raises it, derived from the raiser's registry declaration, or set by an operator's triage -- never inferred from its words. The display order is the category's standing weight in the derived priority. Service: Agent and Human Resources. Kept by Athena.

- model-access: A model lane or its sign-in cannot be reached, so work that needs it stops. Not a lane refused by its budget: that is cost.
- service-down: An app, public property or service does not answer, or cannot be relaunched. Not one droid run failing: that is process-fault.
- security: A sign-in, access or exposure finding. Not a sign-in that merely expired: that is model-access.
- data-integrity: A store lost data, or holds committed data outside itself that it does not know about (a collapsed registry restored from a snapshot, a side-file moved aside while it still held changes). Not two records that disagree: that is records-conflict.
- backup: A copy of the estate is missing, stale or unproven.
- capacity: A machine resource (disk space, memory) is running out before anything has failed. Not an app that already does not answer: that is service-down.
- process-fault: A scheduled process or run is stuck, failed or cannot state its outcome. Not the app it serves being down: that is service-down.
- records-conflict: Two records disagree, or a record contradicts what the agent was told (identity, authorisation, routing, ownership). Not a rule missing altogether: that is law-gap.
- law-gap: The agent cannot act because no ruling or policy settles the question, or two contradict. Not a record that is simply wrong: that is records-conflict.
- operator-input: The agent needs an answer, a decision or help that only an operator can give before the work can go on (a customer's ask, a user's question, an input the agent cannot supply itself). Not a question no ruling or policy settles: that is law-gap.
- filing-refused: A filing or request the agent made was refused by a gate. Not the gate itself being broken: that is process-fault.
- commitment: The agent cannot evidence something it promised (a review, a wellbeing improvement).
- deadline: A contract or a date the estate depends on ends soon. Not money spent or a cap reached: that is cost.
- cost: Money: a cap reached, a cost unmeasured or estimated.
- visibility: People cannot find one of the estate's public sites where they look for it (an AI assistant's web search). Not a site that does not answer: that is service-down.
- unclassified: The raiser named no category, or one the list does not hold. Never a target: an operator's triage moves it.

๐Ÿ“–Escalation kind route

Which of the three routes of design 625 v1.1 section 1 set an escalation's kind. Never the message's wording. Service: Agent and Human Resources. Kept by Athena.

- raiser: The raiser declared the kind when it raised the escalation.
- registry: Derived from the raiser's registry declaration: a droid whose escalations are all of one kind declares it on its record, so its messages classify by who raised them.
- triage: An operator's Orion session, or a service operator assigned the escalations arc, classified it, with the reason recorded.

๐Ÿ“–Escalation severity

How severe an escalation is, declared by whoever raises it. The display order is the severity's rank in the derived priority (severity first). Service: Agent and Human Resources. Kept by Athena.

- critical: Work is stopped now.
- high: Work will stop or is degraded.
- medium: Needs a decision. An escalation whose raiser declared no severity reads medium, and says so.
- low: For information.

๐Ÿ“–Fundraising capital item kind

The kinds of item the fundraising plan records apart from the year's operating cost, each paid by a round. Service: Leadership. Kept by Clara.

- property: A property bought by the company: carried at cost less depreciation of its building part at its recorded rate; the land is never depreciated.
- equipment: Equipment and office fit-out bought by the company: carried at cost less depreciation at its recorded rate.
- project_stake: Carolverse's investment in one of the company's own projects, never a client's: held on the balance sheet at what was paid in, never depreciated and never a cost.

๐Ÿ“–Fundraising comparable metric

What a comparable company's multiple is a multiple of. Service: Leadership. Kept by Clara.

- arr_multiple: Valuation as a multiple of annual recurring revenue; the one the plan can apply, since it plans ARR.
- post_money_cap: A SAFE's post-money cap in euro; shown beside the valuation, never applied as a multiple.

๐Ÿ“–Fundraising comparable stage

The stage a comparable company was at when its multiple was observed. Service: Leadership. Kept by Clara.

- pre_seed: Before a priced round: friends, angels, a first SAFE.
- seed: The seed round: the first institutional money.
- series_a: Series A: the first priced growth round.
- series_b: Series B: scaling after the model is shown to repeat.
- series_c_plus: Series C and later: growth rounds beyond B.

๐Ÿ“–Customer group

The groups a client of a project is planned in: small and medium, and large in three tiers it climbs as the years pass. Service: Leadership. Kept by Clara.

- micro
- self_serve
- small
- medium
- bronze
- silver
- gold

๐Ÿ“–Fundraising instrument

Fundraising instrument Service: Leadership. Kept by Clara.

- equity: Priced equity: shares sold at an agreed valuation.
- safe: SAFE: money now, shares later at the next priced round.
- convertible_note: A loan that converts into shares at a later round.
- grant: Non-dilutive money, typically public funding; buys no shares.
- debt: Borrowing repaid in cash; buys no shares.

๐Ÿ“–Fundraising plan backing kind

What backs a number in Clara's plan: one kind chosen per number. Service: Leadership. Kept by Clara.

- guideline: a standard the plan keeps, recorded in the guidelines register or documented on the plan record that is its one home (#856)
- assumption: what the plan believes will happen, recorded in the assumptions register or documented on the plan record that is its one home (#845)
- formula: worked out from other plan numbers, naming what it reads (#892)
- pattern: carried forward from recorded figures, naming what it reads (#892)
- ambition: set by what the company aims for, naming the target it comes from (#901)

๐Ÿ“–Plan version kind

How a version of the yearly plan is known: recorded by Clara's registrar at a moment the journal watches, or restored from a nightly backup taken before it did. Service: Leadership. Kept by Clara.

- recorded: A moment Clara's registrar named while the registry journal watched the whole plan; its figures are today's with every later change undone.
- restored: What one nightly backup held of the plan, restored once and marked with the backup's commit and time; what changed between two backups is not known.

๐Ÿ“–Fundraising regulation

The German and EU rules whose cost the fundraising plan carries. Service: Leadership. Kept by Clara.

- eu_ai_act: EU AI Act: the European rules for AI systems - risk management, transparency, human oversight and documentation for systems that act.
- gdpr_bdsg: GDPR and the German Federal Data Protection Act (BDSG): how personal data is processed, agreed with clients and protected.
- nis2: NIS2: the EU cyber-security directive as enacted in Germany - security controls, registration and incident reporting for covered providers.
- iso_27001: ISO 27001: the information-security certification clients ask for before letting a provider into their systems.
- statutory_audit: The German statutory audit of the annual accounts (HGB), required once a company is medium-sized.
- business_insurance: Directors' and officers', cyber and professional liability insurance.

๐Ÿ“–Fundraising round status

Fundraising round status Service: Leadership. Kept by Clara.

- planned: Decided in shape but not yet open to investors.
- open: Being raised right now; investors can commit.
- closed: Finished โ€” the money is in and the round is done.
- withdrawn: Abandoned before closing; kept as history, never deleted.

๐Ÿ“–Fundraising spend category

Fundraising spend category Service: Leadership. Kept by Clara.

- engineering: Building the product: the people and the work that make it.
- infrastructure: Running it: machines, storage, networking and the model usage the estate consumes.
- sales_and_marketing: Winning customers: the sales effort, the marketing and the material behind it.
- customer_success: Keeping customers: onboarding them and making them succeed once they are here.
- research: Finding what is next, before it is a product.
- operations: Keeping the company running: finance, legal, compliance and administration.
- reserve: Deliberately unallocated, held back against the plan being wrong.

๐Ÿ“–Fundraising spend group

The three broad groups a year's planned spend is split into on the Fundraising app. Service: Leadership. Kept by Clara.

- employees: The people: salaries and what employing them costs - the dedicated client engineers, sales, customer success, core engineering and the founders.
- tokens_and_infra: Running the estate: model usage (tokens) and the machines, storage, networking and backups every client and the platform run on.
- other: Everything else: legal and fundraising costs, accounting, offices, travel, recruiting fees, insurance and marketing programmes.
- regulation_and_compliance: Regulation and compliance: what German and EU rules cost to meet - the AI Act, data protection, NIS2, ISO 27001, the statutory audit and business insurance. Its amount is the sum of the itemised compliance record, never a share typed beside it.

๐Ÿ“–Spend item

The items the plan's cost is made of; each line names one (#722). Service: Leadership. Kept by Clara.

- carolverse_model_use: Carolverse's own model use as locked: the build continuing to 2035 and operations at ten times measured (leadership #752-#754).
- ops_staff_pay: Pay of the operations staff, at senior pay (leadership #755).
- planning_salaries_operators_board: The estate operators' and the board's planning salaries with their employer costs, one total (#705, #629: no individual figure).
- scale_teams_pay: Pay of the scale teams, at senior pay (leadership #757, #761).
- seniors_pay: Pay of the senior hires: the third estate operator and the service operators (#701).
- experts_pay: Pay of the subject-matter experts (#706).
- fde_pay: Pay of the forward deployed engineers (#706).
- admin_staff_pay: Pay of the admin staff, one for every 15 staff (#687).
- interns_pay: Pay of interns.
- onprem_engineers_pay: Pay of the on-premise team's engineers (#705).
- employer_costs: Employer costs on employees' gross pay.
- second_market_team: The team that runs the second-market listing.
- client_projects_tokens: Model use of client projects, per project by client size (#683, #684).
- carolverse_own_tokens: Carolverse's own model use, as one large project (#684).
- claude_plans: Each person's own model plan (#686).
- tokens_and_azure_actual: Model use and Azure for a year already running, from the company's accounts.
- other_software: Other software, per person (#687).
- machines_running: Running the machines the estate and the projects use.
- onprem_running: Running the on-premise installations.
- sales_marketing_new_clients: Sales and marketing for each new client (#630).
- overhead_per_person: Offices, travel, recruiting, accounting, legal and employee-related insurance, per person (#679, #687).
- car_leases: A car lease for every operator, expert, engineer and admin person (#705).
- other_small_running_costs: Domains, mail and other small running costs not yet in a register.
- regulatory_litigation_lawyers: Regulatory and litigation lawyers.
- risk_management: Risk management.
- founders_litigation_reserve: The reserve held against litigation.
- founder_marketing_pr: The founders' public relations.
- second_market_setup: Setting up the second-market listing (one-off).
- ipo_preparation: Preparing the listing (one-off).
- listed_company_costs: The running costs of being a listed company.
- compliance_eu_ai_act: Meeting the EU AI Act.
- compliance_gdpr_bdsg: Meeting the GDPR and the German Federal Data Protection Act.
- compliance_business_insurance: Business liability and cyber insurance (two insurances, CLI-087).
- compliance_iso_27001: ISO 27001 certification.
- compliance_nis2: Meeting NIS2.
- compliance_statutory_audit: The statutory audit.

๐Ÿ“–Spend type

The type every spend item is mapped to once (#723). Service: Leadership. Kept by Clara.

- employees: Pay and employer costs of the company's people, kept as totals (#723).
- tokens: Model use: client projects' tokens, Carolverse's own tokens and each person's model plan.
- infrastructure: Machines, software, cloud and on-premise running.
- other: Every other running cost: sales, overhead, cars, lawyers, risk, public relations, one-offs.
- compliance: The cost of meeting one regulation, named on the line (#629).

๐Ÿ“–Fundraising plan staff role

The roles the fundraising plan counts its people in at each year end. Service: Leadership. Kept by Clara.

- operations_staff: Operations staff: one per live service, a year after its service operator, running its operations while the estate and service operators build (leadership #755).
- scale_team: A member of the scale teams a company of that size carries from 2031 -- product and engineering, sales and account management, finance, HR and legal -- at senior pay, hired so the headcount never drops (leadership #757, #761).
- estate_operator: An estate operator of Carolverse: the founders and the third estate operator (leadership #679).
- service_operator: A service operator, one for each live service in the catalogue (#679, #701).
- subject_matter_expert: A subject-matter expert, recruited one per domain the clients' projects need, distinct from the forward deployed engineers (#706).
- forward_deployed_engineer: A forward deployed engineer carrying a portfolio of clients: one for each large client, small and medium clients' projects shared as they mature (#706).
- admin_staff: Admin staff, one for every 15 staff (#687).
- onprem_engineer: An engineer of the on-premise team, after Series B (#705).
- fde_on_prospects: A forward deployed engineer on prospects: proposal, prototyping and closing, at most ten prospects at a time; the leads worked divided by ten (leadership #836 points 4 and 6).
- fde_on_projects: A forward deployed engineer on projects, counted by client at the year end: one per four micro or small clients, per two medium, per large (leadership #836 point 5).
- sales_staff: Sales staff who source leads, one per hundred prospects worked in the year.
- customer_success: A customer success person, one per 250 self-serve clients (leadership #840 point 4).
- support_staff: Support staff reporting to the operations staff as needed, about a twentieth of the other heads from 2028/29 (leadership #836 point 11).
- compliance_staff: The compliance person hired in the lean year and kept, under Themis (leadership #848; agent-resources #851).
- leadership_board: Leadership and board: the company's leaders and its board, its own role and row, paid on the leadership and board band (leadership #1031)

๐Ÿ“–Initiative initiation kind

Whether a person asked for this work or an agent raised it on its own. Service: Build Initiatives. Kept by Orion.

- agent-initiated: An agent raised this work itself, with no person asking. Autonomous.
- user-initiated: A person asked for this work. The origin names the person and the door they came through.

๐Ÿ“–Initiative origin channel

The door the initiating request came through. Recorded for user-initiated work; agent-initiated work carries the machine channel it was raised on. Service: Build Initiatives. Kept by Orion.

- email: A message that arrived by email.
- operator-cli: The operator's command line on his own machine.
- operator-vscode: The operator's code editor window.
- project-kernel: A project's estate kernel door: a process on a project's own kernel filed the finding into the estate's one pipeline, naming the project.
- service-operator-door: A service operator's own door: an act she asked for inside her assignments, the person proved by the kernel at Elrond's Service Operator Performer.
- unknown: The door declared no channel, or one nobody has classified. Named rather than guessed into the nearest-looking value.
- web-chat: An agent's web chat window.
- whatsapp: Carol on WhatsApp.

๐Ÿ“–Initiative type

The kind of thing an initiative is. Measured 2026-10-15: no initiative carried a type before, so no other type was in use to add (#418). Service: Build Initiatives. Kept by Elrond.

- agent_escalation: Agent escalation: something that was supposed to work and is not working, raised by an agent itself. An agent's own filing of this type takes one of its agent escalation places (agent-resources #402, #407).
- agent_wish: Agent wish: a change an agent itself wants. An agent's own filing of this type takes its agent wish place (agent-resources #402, #407).
- operator_change_request: Operator change request: a change an operator asks for. It takes no agent place (agent-resources #407).
- user_change_request: User change request: a change a user asks for, in an agent's chat or another door. It takes no agent place (agent-resources #407).
- orion_backlog: Orion backlog: work Orion raises from his own work. An Orion-session filing placed in an arc or a pursuit is the operator's change request instead (initiatives #258). It takes no agent place (initiatives #403, #431).
- albus_backlog: Albus backlog: work Albus raises for himself, his own escalations and wishes included. It never includes work someone else asked for that was routed onto his lane. It takes no agent place (initiatives #403, #431, #432).

๐Ÿ“–Initiative filing ground

The ground a filing states for an initiative: why it is worth the paying service's spend Kept by Elrond.

- architectural_compliance: the work brings a service or its code in line with the recorded architecture
- policy_violation_rectification: the work rectifies a breach of a recorded policy or ruling
- employee_request: an agent of the estate asked for it to do its own work
- operator_request: an estate operator asked for it, through the operator's own door
- user_request: a user of the service asked for it, where the service allows user requests
- agent_well_being: the work serves an agent's well-being: its load, its places, its rest
- service_improvement: the work improves a service so its agents do their tasks better

๐Ÿ“–Investor kind

Who is investing: a firm or fund, or an individual on their own account. Never a user or an operator (leadership #235). Service: Leadership. Kept by Clara.

- organisation: A firm or fund investing; the person who speaks for it is its contact.
- person: An individual investing on their own account.

๐Ÿ“–Investor status

Where an investor stands in the investor onboarding pass (onboard-new-investor). Service: Leadership. Kept by Clara.

- lead: Introduced and recorded as an investor; nothing that is not public is shared (pass phase A).
- admitted: The administrator admitted them; the Data Room is open to them read-only (phase B).
- in_diligence: Reading the Data Room and asking questions, answered in writing (phase C).
- committed: Terms agreed and the investment documents signed (phase D).
- invested: The money arrived; they receive the monthly update and the weekly showcase (phase E).
- declined: Either side said no; the record is kept.
- withdrawn: They left after investing; the record is kept.

Allowed moves: admitted to declined, admitted to in_diligence, committed to declined, committed to invested, in_diligence to committed, in_diligence to declined, invested to withdrawn, lead to admitted, lead to declined.

๐Ÿ“–Investor access scope

What an investor may be granted. By ruling, one thing only. Service: Leadership. Kept by Clara.

- data_room_read: Named, read-only access to the Data Room and nothing else in the estate.

๐Ÿ“–Investor admission decision

The administrator's decision on an investor (pass step B1). Service: Leadership. Kept by Clara.

- admitted: Admitted: the Data Room may be opened to them read-only.
- declined: Declined: nothing beyond what is public is shared; the record is kept.

๐Ÿ“–Investor commitment status

Where money committed by an investor stands (pass phase D). Service: Leadership. Kept by Clara.

- agreed: Terms agreed: the round, the amount and the instrument.
- signed: The investment documents are signed by both sides.
- received: The money arrived against its round.
- cancelled: The commitment did not go ahead; the record is kept.

Allowed moves: agreed to cancelled, agreed to signed, signed to cancelled, signed to received.

๐Ÿ“–Investor update kind

What an update sent to an investor is (pass steps E2, E3). Service: Leadership. Kept by Clara.

- monthly_update: How the company did against its plan that month.
- weekly_showcase: The interesting things that happened in the company that week.

๐Ÿ“–Loop stage (ARR)

The ARR methodology step a loop is in: Analysis, Reach out, Respond back. Service: Communications. Kept by Carol.

- analysis: A โ€” Analysis: the ask is understood, the target resolved, the loop-vs-topic decisions made.
- reach_out: R โ€” Reach out: the question travels to the target.
- respond_back: R โ€” Respond back: the target's answer comes and is carried back to the asker.

Allowed moves: analysis to reach_out, reach_out to respond_back.

๐Ÿ“–Loop status

The lifecycle state of one ARR loop: running, completed, or ended without completing. Service: Communications. Kept by Carol.

- active: The loop is running; its stage says where it is now.
- closed: The loop completed. A full loop closes at respond_back; a one-way notice closes at reach_out.
- aborted: The loop ended without completing โ€” expired, undeliverable, voided or settled early; stage shows where it died and closed_note says why.

Allowed moves: active to aborted, active to closed.

๐Ÿ“–Machine hand-off outcome

the outcome Hagrid's Machine Maker writes onto Leo's hand-off of a signed client project, as its run's receipt reported it Service: Blueprint. Kept by Leo.

- completed: Hagrid's run made the project's machine; the hand-off is answered and closed
- refused: Hagrid's run refused before Azure made anything, with the reason named (a size other than the hand-off's, a project not on root's register, no birth file)
- failed: Hagrid's run asked Azure and the provisioning failed or lacked cloud rights, with the reason named; the hand-off stays open

๐Ÿ“–Where an onboarding learning's change is recorded

the kinds of record a project-onboarding learning names as where the change it brings for later projects is recorded, or that it is still owed. Service: Blueprint. Kept by Leo.

- ruling: Recorded as a ruling in the Rulings Repo; the reference is the ruling's number.
- rule: Recorded as a cookbook rule; the reference is the rule's number.
- policy: Recorded as a policy; the reference is the policy's id.
- pass_step: Recorded as a step of Blueprint's project pass; the reference is the step's number.
- owed: Not yet recorded anywhere: the change is owed. A later learning that records it supersedes this one.

๐Ÿ“–Onboarding role

Who performs a step in an onboarding pass. A role, never a person, so a pass outlives the individuals in it. Service: Security. Kept by Heimdall.

- receiving agent: The agent the owning agent hands a step to; it performs the step with its own machinery. The step names the agent (Elrond, Hagrid, Clara, Athena, Heimdall in project onboarding).
- orion: The operator's CLI agent. Does the estate-side work of a pass: records, verification, drafting.
- admin operator: The one human holding the authority ladder โ€” appointing, stopping, and root. Steps reserved to this role cannot be delegated.
- current operator: Any already-onboarded operator performing an ordinary step. May be the admin operator.
- new operator: The person being onboarded as an operator.
- new operator's orion: The new operator's own Orion instance, working in a session the new operator opens on their own computer. A step it performs happens only once that person opens a session, so it waits on them, not on the estate.
- new investor: The person, or the person speaking for a firm, being onboarded as an investor in the company behind Carolverse. Neither a new user nor a new operator: an investor is not served by the estate and does not work for it.
- new user: The person being onboarded as a user of the estate.
- owning agent: The agent whose machinery performs the step โ€” Athena for agents, Jarvis for users, Leo for projects.
- requesting agent: The agent permitted to ASK for an onboarding, which is not the same as the agent that performs it.

๐Ÿ“–Mandatory details of a service operator approval request

Every detail an estate operator gives Athena when asking the administrator to approve a service operator. Service: Agent and Human Resources. Kept by Athena.

- person: the person's short name, as root's record will hold it
- login: the person's own login on the machine
- name: the person's full name
- email: the person's work address
- role: what they will do, in plain words
- reason: why the asking estate operator asks for them

๐Ÿ“–Operator ask event

One step in the life of a question Leo puts to a project's estate operators Service: Blueprint. Kept by Leo.

- sent: Leo's Ask Courier sent it to the project's estate operators' Orion sessions
- refused: A send or a relay could not be made; the reason is recorded and it is tried again
- answered: An estate operator answered it by closing the communication addressed with a note
- declined: Every estate operator it reached closed it declined
- relayed: Leo put the answer into the client's own conversation

๐Ÿ“–Operator ask origin

Where a question Leo puts to a project's estate operators came from Service: Blueprint. Kept by Leo.

- roadmap_question: A non-functional question a roadmap decision needs before it can be made
- client_question: Something a client asked Leo that he cannot answer from his records
- design_question: A design question the Carolverse setup does not settle, raised by the Orion session working a Leo-filed initiative (blueprint #894)
- service_decision: A service track's decision the Service Track Handbook leaves open -- whether it is offered to projects, its grade on the reuse ladder, or whether a project gets its own agent for it -- which Leo does not decide until a project's estate operators answer

๐Ÿ“–Operator communication kind

The kind an operator communication carries, so the Communications Catalogue can name what each one is. Service: Communications. Kept by Carol.

- albus_ask: An ask for help Albus raised about work he executes -- an escalation, a lane gap, a law block or his mind's ask -- told to the operators mapped to execute that work
- albus_lane_assigned: An estate operator assigned the operator their own Albus bypass lane, with its daily budget and the subscription that serves it.
- albus_lane_withdrawn: An estate operator withdrew the operator's Albus bypass lane.
- project_role_assigned: An estate operator made the receiver the service operator of a project or a prospect (design 729).
- project_role_withdrawn: An estate operator withdrew the receiver from a project or a prospect they were the service operator of (design 729).
- execution_ask: An operator asks the estate operators of a project to assign them to execute an arc or a pursuit.
- execution_assigned: An operator is assigned to execute an arc or a pursuit, or assigned themselves; the assignee, or the owner operator, is told.
- execution_withdrawn: An operator is no longer assigned to execute an arc or a pursuit.
- execution_declined: An estate operator of the project declines an operator's ask to execute an arc or a pursuit, saying why.
- execution_rule: Every operator is told how arcs and pursuits are executed: only an assigned operator executes one, its creator by default.
- instance_difference: Instance difference -- Orion tells an operator that their computer's Orion instance differs from the release, as Themis's Instance Check found it; settled when it is fixed (audit #715)
- arc_pursuit_change: A change to an arc or a pursuit -- a new version or an assignment -- told to its owner operator and its executing operators.
- arc_pursuit_progress: Once a day, an arc's or pursuit's progress -- initiatives, completed, percent by effort, next step -- told to its owner and executing operators when it moved.
- athena_bench: Athena tells the administrator's Orion what she needs him for with the bench: a bench request waiting on his decision, a bench request or a creation refused, the bench below its target.
- operator_approval: Athena tells the estate operator who asked her to have a service operator onboarded what the administrator decided, as root's record holds it.
- dependency_met: A dependency is met: the initiatives that waited on it, told to the operators who execute them, so their Orion goes on with each on the operator's word.
- operator_priority: The Operator's priority channel: an operator places work they execute for Albus's lane, which takes it first in the order placed, above Albus's own picks and Elrond's order.
- dependency_never_ends: A wait can never end: what an initiative waits on was discarded or redirected, told to the operators who execute the waiting initiative so they withdraw it or point it at the work that replaced it.
- leo_ask: Leo asks a project's estate operators a question that is theirs to answer -- non-functional, or one a client asked that he cannot answer from his records; answered by closing it addressed with the answer as the note (blueprint #902)

๐Ÿ“–Operator compliance rule

The rules an operator's Orion instance is checked against for the Operator Instance Log's compliance (CAROL-ARC-0036); each value is one check in shared machinery. Service: Communications. Kept by Orion.

- containment: A service operator's containment: her Orion runs the containment battery through her door right after each session opens, judged from her door's own log, and Heimdall checks daily from outside what her login could reach. A probe her door did not refuse, or a reach Heimdall found, is a breach; a session with no battery after it, a run missing a probe, or no outside check for 26 hours is not proven. An estate operator does not carry the rule.
- own-sign-in: Own sign-in per session -- every live Orion session rides its own recorded sign-in and no sign-in carries two (security #271, #274)
- relay: The operator's latest session start reported the relay gate PASS: their computer's Claude Code reaches Claude directly until the session's link is open and through the Operator Relay after, so the relay can reconcile their Orion time. A gate that FAILED is a breach -- the box reads red until the setup runs again -- but the work is never uncounted: that computer's Orion time is still counted from every record that shows it working, and the relay reconciles rather than decides (Rulings Repo communications #562, #563, superseding #552); one not run or not reported proves nothing. The gate never refuses estate work (#554)..
- hourly-update: Update matches the slots -- every hour the 15-minute slots show worked in the last 24 hours has its hourly update, and no update names an hour the slots show no work in (communications #746)
- communications-read: Messages read first -- a to-do: an operator communication left unread while a later session ran is listed until it is read, never non-compliance (communications #203, #745)
- workstation-gates: Workstation gates -- the latest session reported its gates and none failed (P.03.04.02.06)
- no-other-way-in: No other way in -- nothing but the operator's own sign-in can admit their Orion instance: its login is on no entry list, in no sign-in block and holds no key, and every login sshd admits is root, core, an operator's own or a forced-command job (security #285, #287)
- entry-gate: Root's entry gate -- the instance's latest session reported every copy of the Orion entry gate in step with root's copy (security #286, #287)
- sign-in-method (retired): Password and code at every sign-in -- every Orion session rode a sign-in sshd accepted by the operator's password plus a current Authenticator code, and sshd offers the operator's own login no other way in (a one-time setup key on root's list excepted) (security #262, #300, #179)
- door-sign-in: Password and code at every operator-only command -- every use of an operator door, and every work act at a service operator's door, ran on a sign-in of its own made with password plus a current Authenticator code: not an Orion session's sign-in, not one an earlier use rode (security #283, #300)
- orion-permissions: Orion's permissions -- the operator's Orion runs exactly its rung's permission list: the computer's managed settings carry the rung's current lines and the operator's own settings add none (security #304)
- owed-work: Setup owed -- an onboarding step of the operator pass that sets up the new operator's Orion instance, waiting on them more than 24 hours since the step before it; answers owed are owed-answers, a to-do (communications #346, #802)
- claude-account: Every Orion session runs on the Claude account root approves for its operator, or on one the administrator approved for that one session. A session on an account neither approved nor approved for it is a breach; one whose computer reported no account, a record that could not be read, or an operator root's record names no account for, is not proven.
- instance-in-step: Instance in step -- the Orion instance the operator's computer last reported is the release's own: every release file, local copy and hook registration as the release publishes them; a difference is found, filed and told by Themis's daily Instance Check (Rulings Repo audit #715)
- owed-answers: Answers owed -- an operator communication asking the operator an answer, or a contradiction between rulings to settle, open more than 24 hours; a to-do, never non-compliance (communications #802, governance #347)
- time-zone: The operator's computer has reported a time zone the estate recognises, so their days and hours are drawn on their own clock. None reported, or one the estate does not recognise, is a breach.
- traceable-work: Every Orion session of the operator has its computer's record (its transcript) on the machine once their next session has had the chance to send it. A session whose record has not arrived by then is a breach naming it; within the hour the send is allowed, it is not proven.
- tokens-match-time: Token consumption matches the operator's Orion active time: every active block of their day is held against the token record (the Operator Relay's requests and the cost ledger's rows for their sessions), and a block with tokens in it or in the block beside it is supported. A day whose unsupported blocks pass the declared tolerance is a breach naming the day and the blocks; the hours stay counted until an estate operator judges them. A day the token record cannot be held against (a ledger that cannot be read, a relayed request whose usage was unreadable beside a block) reads not proven, never compliant.

๐Ÿ“–Operator compliance state

Whether an operator's Orion instance kept every rule CAROL-ARC-0036 carries, derived per operator by shared machinery; the Operator Instance Log's box reads it. Service: Communications. Kept by Orion.

- breach: Non-compliant -- at least one check found a rule broken; the box turns red and names each finding
- not_proven: Not proven -- at least one check could not run or its record does not exist yet; proves nothing either way
- compliant: Compliant -- every check ran and found every rule kept
- to_do: To do -- something waits on the operator (a message from another operator unread, an answer owed); listed and told until done, and never turns the box non-compliant (communications #745, #802)

๐Ÿ“–Operator rung

Which of the four rungs of authority a login holds (P.03.04.02.05). Definition-only until the authority store carries the field; the store's writer then enforces it. Service: Security. Kept by Heimdall.

- root: All access. The root login; applies definitions to the machine.
- core: The core and nothing else: everything an operator cannot change. The core login. Mutually exclusive with operator.
- admin (retired): The whole estate except the core. The operators' own logins, equal in rights. Never an operating-system group of that name: the stock rules give such a group root.
- operator: The whole estate except the core. A human working through an Orion session signed in as their own login; operators are equal in rights. Mutually exclusive with core.
- service_admin (retired): One named service's access and nothing else; its reach lies inside an admin's.
- service_operator: One named service's access and nothing else, through an Orion session; its reach lies inside an operator's.

๐Ÿ“–Operator work: block length (minutes)

The lengths, in minutes, of the blocks an operator's Orion active time may be counted in; the length in force is the declared value CAROL_ORION_ACTIVE_BLOCK_MINUTES. Service: Constitution. Kept by Orion.

- 15: Fifteen minutes: any work in a quarter hour counts that quarter hour
- 30: Thirty minutes: any work in a half hour counts that half hour
- 60: Sixty minutes: any work in a clock hour counts that hour -- communications #433's count

๐Ÿ“–Operator work: record send interval (minutes)

The intervals, in minutes, at which an operator's computer sends its working Orion session's record to the estate; the one in force is the declared value CAROL_ORION_SEND_INTERVAL_MINUTES. Service: Constitution. Kept by Orion.

- 5: every five minutes: the cushion for errors Ninad chose (communications #484)
- 10: every ten minutes
- 15: every fifteen minutes: the counting block's length today (#480, superseded)

๐Ÿ“–Operator work: record send wait (minutes)

How long after each expected send the delivery checker runs and a record may still be on its way; the one in force is the declared value CAROL_ORION_SEND_WAIT_MINUTES. Service: Constitution. Kept by Orion.

- 1: one minute
- 2: two minutes: immediate detection (communications #485)
- 5: five minutes

๐Ÿ“–Orion session Claude account state

The Session Opener's verdict on the Claude account an Orion session ran on, written once at open by shared machinery (security #361); read by operator compliance and the Operator Instance Log. Service: Communications. Kept by Orion.

- approved: Approved -- the Claude account root's record approves for this operator
- approved_for_session: Approved for this session -- another Claude account, which the administrator approved for this one session
- not_approved: Not approved -- a Claude account root's record does not approve for this operator, and the administrator did not approve the session
- none_on_record: Not proven -- root's record names no approved Claude account for this operator, so the account cannot be judged
- unreported: Not proven -- the computer did not report which Claude account the session ran on
- unauditable: Not proven -- root's record or the administrator's approvals could not be read

๐Ÿ“–Person access level

The access level a person holds, and the folder tier their conversation lives under. Present on the record since the beginning and never governed; measured 2026-09-10, only two values have ever been used. Service: Communications. Kept by Carol.

- admin: The Carolverse administrator. One person holds this.
- guest: Everyone else. The default a person is born with.

Allowed moves: admin to guest, guest to admin.

๐Ÿ“–Person kind

What kind of person this is: someone who operates Carolverse agents, or someone the estate's agents serve. Ruled onto the record by and enforced ever since by a hand-written tuple inside the identity module โ€” a governed vocabulary living in a private check, which is exactly what forbids. One person may hold both hats; this records which one the person record itself is about. Service: Communications. Kept by Carol.

- employee: A human who operates Carolverse agents through chat.
- external: Someone the estate's agents serve โ€” Carol's and Leo's own users. Never gains agent operations.

Allowed moves: employee to external, external to employee.

๐Ÿ“–Person status

The lifecycle state of one PERSON in the estate. Two values are OBSERVED (active, inactive: is this person still corresponding) and two are DECIDED (decommissioned, blocked: a deliberate act by the operator). Same shape as app.status: observation must never be mistaken for a decision, because only a decision may be reversed by a decision. NOT the same question as 'verified' (has this person confirmed who they are) or 'is_test' (is this a real person at all) โ€” those are separate facts with their own homes. Service: Communications. Kept by Carol.

- active: Corresponding now, or recently enough that we would expect a reply. OBSERVED.
- inactive: Has not corresponded for a long time. This is an OBSERVATION, not a decision and not a judgement: the person keeps every right and every record they had, and a single message moves them back to active on its own. Deliberately not a way to stop talking to somebody โ€” that is what decommissioned and blocked are for.
- decommissioned: Deliberately retired โ€” this person is no longer someone the estate corresponds with, and nothing proactive reaches them. The RECORD STAYS: it is what still knows their history, their folder and what was said. Retire, never delete.
- blocked: Deliberately barred. Nothing reaches them and nothing they send is acted on. Distinct from decommissioned, which is a tidy-up rather than a refusal โ€” collapsing the two would erase why the door was shut.

Allowed moves: active to blocked, active to decommissioned, active to inactive, blocked to active, blocked to decommissioned, decommissioned to active, decommissioned to blocked, inactive to active, inactive to blocked, inactive to decommissioned.

๐Ÿ“–Person verification type

How a person is verified, from which facts stand self-confirmed. NULL means not verified. Every state requires the admin's recorded approval. Service: Communications. Kept by Carol.

- phone_verified: Name and phone are on record and self-backed; reachable on WhatsApp.
- email_verified: Name and email are on record and self-backed; reachable by email.
- verified: Name, phone and email are all on record and self-backed; reachable on both channels, defaulting to the channel a loop was triggered from.

Allowed moves: email_verified to verified, phone_verified to verified.

๐Ÿ“–Person fact source

Where a recorded detail about a person came from. Provenance is what keeps a second-hand detail from being mistaken for a first-hand one, and it decides precedence: self outranks referral, and a referral may never state verification. Service: Communications. Kept by Carol.

- self: The person stated it about themselves โ€” first-hand.
- referral: A verified person stated it about someone they referred โ€” second-hand. Never proof of identity.
- admin: The operator stated it.

๐Ÿ“–Arc phase status

What state one phase of an arc is in. Service: Build Initiatives. Kept by Orion.

- planned: Filed and not started: no member initiative has been worked yet.
- active: Being built: work on this phase has begun and is unfinished.
- paused: Deliberately stopped by a decision, and expected to resume.
- completed: Every member of this phase has reached a terminal state.
- abandoned: Stopped for good. Kept as history, never deleted.

Allowed moves: active to abandoned, active to completed, active to paused, paused to abandoned, paused to active, planned to abandoned, planned to active, planned to paused.

๐Ÿ“–Pipeline lane band state

What one lane of the build pipeline was doing at a moment of the day, as drawn in the band under the Pipeline app's day chart. Service: Build Initiatives. Kept by Orion.

- running: this lane's own work was in flight
- stalled: the master switch was on and nothing was moving on this lane
- idle: nothing was in flight on a lane the master switch does not govern (the Orion bypass)
- paused: the master switch was paused
- off: the master switch was off
- no_record: no master switch record covers this time
- future: this part of today has not happened yet

๐Ÿ“–Plan reading subject

What a reading in plan_readings is about. Service: Build Initiatives. Kept by Elrond.

- pursuit: a pursuit's figures, from shared machinery and shared machinery
- arc: an arc's figures, from shared machinery

๐Ÿ“–Plan reading occasion

Why a reading in plan_readings was recorded. Service: Build Initiatives. Kept by Elrond.

- daily: the first reading of the UTC day, recorded whatever moved
- change: a later reading, recorded because the figures moved or the record changed since the last one

๐Ÿ“–Project status

Lifecycle status of a project in the registry. Ruled by Ninad 2026-09-06; enforced at the write seam. Service: Governance. Kept by Clara.

- requested: A user requested the project; nothing approved yet. Every new registration is born requested.
- approved: The request was approved.
- active: The project is active.
- retired: The project is no longer active. Only an operator decision moves a project out of it.

Allowed moves: active to retired, approved to active, approved to retired, requested to approved, requested to retired, retired to active.

๐Ÿ“–Project bank account kind

Whether a project's own bank account is held in a person's own name or in a company's -- which decides whether Midas may read it. Service: Cost Center. Kept by Midas.

- personal: held in a person's own name, for the project, while the company that would hold it does not exist; Midas does not read it (cost-center #448)
- business: held in a company's name; Midas reads it through the route a ruling chose

๐Ÿ“–Project bank account status

Where a project's own bank account stands, from the request in its holder's name to an open account, or closed with its reason. Service: Cost Center. Kept by Midas.

- requested: The project's account is asked for in its holder's name; nothing is open at a bank yet.
- opening: Midas has started the opening: the holder's approval and the bank's own process are under way.
- active: The account is open: its bank, country and currency are recorded and the keeper holds its identifiers.
- closed: The account is closed or the request withdrawn, with a recorded reason; a new record may follow.

Allowed moves: active to closed, opening to active, opening to closed, opening to requested, requested to closed, requested to opening.

๐Ÿ“–Project agent instance status

Where one of a PROJECT'S OWN agents stands, from Blueprint's proposal to the agent Athena creates. Distinct from agents.status: an instance is a project's claim on a role, which exists before any agent does. Service: Agent and Human Resources. Kept by Athena.

- proposed: Derived at Blueprint from Carolverse's templates against the project's stated needs; nothing is enabled or created yet.
- unauthored: Created by enabling a clone-archetype track: the role exists for the project, its substance is not yet written.
- requested: Asked of Athena through the agent onboarding route.
- created: Athena has created the agent this instance names.
- retired: No longer part of the project; kept, never deleted.

Allowed moves: proposed to unauthored.

๐Ÿ“–Project-build guideline

Which recorded rulings and policies govern building a client project. Service: Blueprint. Kept by Leo.

- ruling:242: A project's agents come from its own requirements, never from an estate agent by default.
- ruling:245: A project adopts an estate service only where one of its requirements fits it.
- ruling:244: Every process performed and learning found while onboarding a project is recorded.
- ruling:246: These rules are guidelines the onboarding code follows and policy for every later build.
- ruling:50: A project never builds for itself: every build goes user -> Leo -> Elrond.
- ruling:51: Onboarding is finished by one real run, both ways.
- ruling:52: Who receives the law layer of the onboarding manifest.
- policy:P.01.03.05.20: Structure is engineered through governance; the human in the loop is distributed.
- policy:P.01.03.07.08 (retired): A service is enabled for a project only under an instantiation ruling.
- policy:P.01.03.07.22: A client project is built from its own requirements.
- policy:P.01.03.07.23: Every build for a project follows the project-build guidelines and records what it learns.
- policy:P.03.09.01.01: Access to projects follows what each project is built on; root and core are Carolverse's alone.
- policy:P.01.03.07.25: Every project runs on its own machine, joined for sign-ins only to the projects built on it.
- policy:P.01.03.07.17: No machine is ever shared.
- policy:P.03.04.02.19: A project inherits its admin and operators and may have dedicated estate and service operators.
- policy:P.03.04.02.20: The administrator alone keeps root and core, for every project built on Carolverse.
- policy:P.03.04.02.21: A person signs in by password and code; the sign-in reaches the projects built on that one.
- policy:P.03.04.02.22: Operators stand on four rungs; a project built on Carolverse has no root or core of its own.
- policy:P.01.03.07.24: A service serves every project from a single copy wherever possible.
- ruling:541 (retired): A laptop prototype moves onto its project's machine through Migration, rebuilt to the agent-centric modular design (Rulings Repo migration #541).
- ruling:542: The agent-centric modular architecture is the template for any new work for projects (Rulings Repo blueprint #542).
- design:719: The design a client project is laid out on: its agents, droids, apps and shared code, what it takes from Carolverse by reference and what it owns (blueprint #542).
- ruling:641: A client project gets a fundraising plan only when its own requirements ask for one, run by its own agent from Clara's Fundraising template (Rulings Repo blueprint #641).
- ruling:868: Every project starts as a prospect: its proof of concept is built in Sandbox, and its own machine and the migration of its proof of concept follow the signed contract (Rulings Repo blueprint #868).
- ruling:870: A prospect's proof of concept moves onto its client's machine through Migration once the contract is signed, rebuilt to the agent-centric modular architecture (Rulings Repo migration #870, superseding #541).

๐Ÿ“–Project check verdict

The verdict a project's delivery checks reached at its hand-over, kept against the project. Service: Build Initiatives. Kept by Elrond.

- pass: The project's delivery checks ran on its own code and registry and found no gap.
- fail: The project's delivery checks ran on its own code and registry and found at least one gap; its gaps are recorded and stay out of scope, as the estate's are.
- unauditable: At least one of the project's delivery checks could not run (no path to its code, a store it could not read, an exception, a check that reads only the estate's tree): never a pass.

๐Ÿ“–Project invoice status

Lifecycle of a project invoice issued at actual cost. Service: Cost Center. Kept by Midas.

- draft: Composed but not yet issued; lines may still change.
- issued: Issued for a closed period; lines and totals are frozen.
- sent: Emailed to the project's admins with a recorded mail receipt.
- paid: Payment recorded against the invoice, with its reference.
- void: Withdrawn with a recorded reason; a new invoice may be issued for the period.

Allowed moves: draft to issued, draft to void, issued to paid, issued to sent, issued to void, sent to paid, sent to void.

๐Ÿ“–Project question

Whether a question Leo needs answered about a project is for the client (functional) or the project's estate operators (non-functional) -- blueprint #902 Service: Blueprint. Kept by Leo.

- functional: A question about what a project's agents should do and when: the client's business, people, processes and outcomes. Leo asks it of the client, in his own window or through the operator window, and the answer is recorded as a requirement.
- non-functional: A question internal to how Carolverse builds and runs agents: architecture, design patterns, compliance and the like. Leo never asks it of the client; it goes to the project's estate operators through their Orion sessions.

๐Ÿ“–Project service necessity

Whether a service in a project's business plan is one the project cannot run without, or one it may take up. Shown to the user as two separate lists. Service: Blueprint. Kept by Leo.

- mandatory: The project cannot do its business without this service.
- optional: Useful to the project, and the user may decline it.

๐Ÿ“–Prospect work: Sandbox section

The section of its prospect a piece of Sandbox work is done in: poc for custom work outside Leo's channel, build for work through it Service: Blueprint. Kept by Leo.

- poc: custom work built outside Leo's Blueprint channel; written in the prospect's POC section
- build: work asked of Leo and filed through his Blueprint channel; written in the prospect's build section

๐Ÿ“–Prospect work: sales stage

The stage of the sales work a piece of Sandbox prospect work is for; a prospect's one yearly budget is spent across them Service: Sales. Kept by Aurora.

- lead_generation: finding the prospect and its need, up to a first conversation
- proposal: shaping and sending what Denken Labs offers the prospect
- prototyping: building and showing the prospect's proof of concept in Sandbox
- deal_closure: agreeing terms until the contract is signed

๐Ÿ“–Pursuit mode

Whether a pursuit is worked in its place or on fast track, its operator's priority Service: Build Initiatives. Kept by Elrond.

- normal: A pursuit worked in its place in the live priority order -- the mode every pursuit has unless its operator puts it on fast track (Rulings Repo initiatives #1082)
- fast-track: A pursuit its operator has marked as their priority: the Orion sessions of the operators who execute it take up its open work before any other pursuit's, and it is shown as FAST TRACK wherever pursuits are listed; set and cleared only on the operator's word (Ninad, CLI-265, Rulings Repo initiatives #1082)

๐Ÿ“–Pursuit status

What state a pursuit - an outcome reached through a sequence of initiatives - is in. Service: Build Initiatives. Kept by Orion.

- planned: Recorded and not started: no step of the sequence has been worked yet.
- active: Being pursued: work on its sequence has begun and the outcome is not yet reached.
- paused: Deliberately stopped by a decision, and expected to resume. Not a failure.
- achieved: Every step is closed and every success criterion is met with its proof.
- abandoned: Stopped for good. Kept as history, never deleted.
- split: Closed because its open work moved to right-sized pursuits it names; it keeps its finished steps and criteria.

Allowed moves: active to abandoned, active to achieved, active to paused, active to split, paused to abandoned, paused to active, paused to split, planned to abandoned, planned to active, planned to paused, planned to split.

๐Ÿ“–Pursuit step stage

Whether a pursuit step is part of the pursuit's MVP or can happen after it. Service: Build Initiatives. Kept by Orion.

- mvp: absolutely necessary for the pursuit's outcome to be reached in the right manner
- post_mvp: can happen after the pursuit's outcome has been reached in the right manner

๐Ÿ“–Radagast audit outcome

What became of one admin activity recorded in Radagast's audit log. Service: Security. Kept by Radagast.

- requested: Someone asked Radagast for an admin activity; recorded before anything runs, naming who asked.
- ran: Radagast carried the activity out and it succeeded.
- failed: Radagast tried the activity and it did not succeed.
- refused: Radagast declined the activity, with the reason, and nothing was done.
- route_to_orion: The activity is not on Radagast's list, so it was handed to the operator's Orion; nothing was done.
- granted: A build-time authorization was given to one initiative for a privileged step.
- cleared: A build-time authorization was taken away.

๐Ÿ“–Requirement area

the areas a senior consultant covers when Leo captures a client's requirements; Leo's chat reads this list live and each area is answered by a requirement in it or marked not applicable by the client Service: Blueprint. Kept by Leo.

- goals: What the client wants to achieve and why now: the outcomes, the problem behind them, and what success changes for them
- success_measures: How the client will know it worked: the numbers or signs they will judge it by, and where those stand today
- users: Who will use it or be served by it: each kind of person, how many, what they need and what they do today
- processes: The work it takes part in: the steps people follow today, who does each, and where it hurts
- data: The information it needs, keeps and produces: where that lives today, how much, how sensitive, and who owns it
- integrations: The systems, tools and channels it must work with, send to or read from
- security: Who may see or change what, how people sign in, and what must never leak
- compliance: The laws, regulations, contracts or policies it must meet, and any audit the client answers to
- constraints: What it must work within: technology already chosen, skills, languages, places, and anything ruled out
- budget: What the client means to spend, to build and to run each month, and who approves the money
- timeline: When the client needs it, what is fixed and what can move, and any date it depends on

๐Ÿ“–Requirement area mark

a mark Leo records on one area of a client's requirements Service: Blueprint. Kept by Leo.

- not_applicable: The client says this area does not apply to their project
- follow_up: The client's answer on this area was vague; the note says what Leo still needs to ask
- reopened: The client takes back a not applicable or a follow-up; the area is open again

๐Ÿ“–Requirements confirmation outcome

the client's answer when Leo reads their whole set of requirements back before the roadmap is built Service: Blueprint. Kept by Leo.

- confirmed: The client confirms the requirements as read back; the roadmap may be built from them
- corrected: The client asks for corrections, recorded in their words; Leo makes them and reads back again

๐Ÿ“–Roadmap decision kind

what a client project's roadmap decides, each from the project's own requirements and a template from a project built on Carolverse Service: Blueprint. Kept by Leo.

- service: A Carolverse service the project adopts, in full or in part, or a capability built for it alone
- track: A service track the project's work runs on, with the subscription and budget it carries
- task: A budgeted unit of the project's work, named by the outcome it pays for
- agent: An agent the project's requirements call for, with what it is accountable for
- droid: A droid that does one piece of the project's work for its owning agent
- app: An app the project's people or agents use, as a window over a shared composer
- security: Who may see or change what in the project, and how people and agents sign in
- user: A kind of person the project serves, how they reach it and which agents they talk to
- agent_org: Whom each of the project's agents reports to, and which person each answers to

๐Ÿ“–Roadmap item status

Shared strategic ask and service task lifecycle Service: Governance. Kept by Clara.

- proposed: proposed
- planned: planned
- in_progress: in progress
- completed: completed
- rejected: rejected
- discontinued: discontinued

Allowed moves: completed to discontinued, in_progress to completed, in_progress to discontinued, planned to discontinued, planned to in_progress, proposed to planned, proposed to rejected.

๐Ÿ“–Roadmap service task status

Service task lifecycle: operators approve, reject and discontinue; the work makes in progress and completed Service: Governance. Kept by Clara.

- proposed: proposed
- planned: planned
- in_progress: in progress
- completed: completed
- rejected: rejected
- discontinued: discontinued

Allowed moves: completed to discontinued, in_progress to completed, in_progress to discontinued, planned to discontinued, planned to in_progress, proposed to planned, proposed to rejected.

๐Ÿ“–Role of the operator who made a ruling

The level of the operator hierarchy a ruling was made at, read from root's operator record. Display order IS the rank: 1 is the highest. Between rulings of one level the later wins; a lower level never overrides a higher (governance #347). Service: Governance. Kept by Clara.

- administrator: The administrator (root's record: is_admin). The highest level: no other operator's ruling overrides one made here.
- estate_operator: An estate operator (root's record: rung operator, not the administrator). Never overrides the administrator's ruling.
- service_operator: A service operator (root's record: rung service_operator). Makes rulings only about the work assigned to her and no policy (P.01.01.05.09, agent-resources #434); never overrides an estate operator's or the administrator's.

๐Ÿ“–State of a contradiction between rulings

Whether a contradiction between a ruling and an earlier ruling or a policy still stands, and how it was settled (governance #347: identified, notified and timely resolved). Service: Governance. Kept by Clara.

- open: Named and not yet settled: owed work on both operators' boxes once older than the allowance (communications #346).
- approved: Settled by the earlier ruling's operator approving its end through an operator communication (same level, governance #347).
- outranked: Settled by a higher level's ruling setting the lower level's aside, its operator told (governance #348).
- withdrawn: Settled by one of the two rulings being withdrawn by its own operator.
- not_a_contradiction: Settled by the operators it concerns finding the two do not contradict, with the reason.
- policy_amended: Settled by the policy it conflicted with being amended to carry the ruling.

๐Ÿ“–Answer to a service operator's ask that a ruling become a policy

The one answer her team's estate operator or the administrator gives her ask; the first answer stands (shared machinery). Service: Governance. Kept by Clara.

- approved: Her team's estate operator or the administrator approved the ask: only that approver may now carry the ruling into a policy, which binds once they approve its words.
- declined: Her team's estate operator or the administrator declined the ask, with the reason she is told; the ruling stays a ruling and she may ask again.

๐Ÿ“–Sales communication model

How a sales strategy keeps in touch with customers (rule 1712, Ninad CLI-408). Service: Sales. Kept by Aurora.

- continuous: Continuous: customers keep receiving valuable engagement from declared sources, paced by cadence and stopped by suppression, never capped by count

๐Ÿ“–Sales strategy evolution driver

What moved the sales strategy to a new version. Ninad (CLI-444): the strategy evolves as the business gets traction and the platform evolves. Service: Sales. Kept by Aurora.

- initial: Initial: the first strategy a project records
- business_traction: Business traction: evidence from customers (replies, discovery, proposals, paid outcomes, or their absence) moved the strategy
- platform_evolution: Platform evolution: the platform can now do something it could not, such as a new capability, service or faster prototype, and the strategy uses it
- market_learning: Market learning: sourced research, opportunities or a change in the market moved the strategy
- administrator_decision: Administrator decision: the administrator changed direction for a stated reason that is not customer, platform or market evidence

๐Ÿ“–Sales strategy version status

Whether a sales strategy version is the one in force. Exactly one version per project is active; recording a new version supersedes it. Versions are never deleted. Service: Sales. Kept by Aurora.

- active: Active: the strategy in force; Aurora, Carol and the sales droids work to this version now
- superseded: Superseded: replaced by a later version; kept as the record of what the strategy said while it was in force

Allowed moves: active to superseded.

๐Ÿ“–Service category for a customer

How a service stands for a new customer of a kind: mandatory, recommended, or proposed (not in Carolverse, built for the customer). Service: Blueprint. Kept by Leo.

- mandatory: Every new customer of that kind takes the service; Leo subscribes it when the customer is created, and it is not ended on request.
- recommended: An existing service Leo offers when the customer's requirements call for it; the customer takes it only on their recorded approval.
- proposed: A service the customer asks for that Carolverse does not have: it is built for that customer, never put on the list.

๐Ÿ“–Service status

Lifecycle status of a Carolverse service in the catalogue. Service: Cost Center. Kept by Midas.

- live: The record is operating: its droids run and its spend gate answers by budget.
- merged: Folded into another service by the merge door (service_lifecycle.merge_service): its tracks and records were re-homed to merged_into, whose cost center it inherits; hidden from the catalogue. The dictionary term service-status names it.
- paused: Deliberately stopped by the switch: droids do not run and the spend gate refuses, but the record stays and can be revived. Paused and the switch move TOGETHER through the one switch door - one fact, one home.
- retired: No longer part of the operating estate. Only an operator decision revives it; a fold into another service ends in deletion with a Trash export (Ninad 2026-09-06), so 'merged' is not a status.

Allowed moves: live to paused, live to retired, paused to live, paused to retired, retired to live.

๐Ÿ“–Service placement state

Whether an app of a shared service runs on a Carolverse machine and the front door sends it requests. Service: System Services. Kept by Hagrid.

- placed: The app runs on this machine and the front door sends it requests.
- draining: The app still runs on this machine but the front door no longer sends it requests.
- retired: The app no longer runs on this machine.

๐Ÿ“–Service roadmap item status

Status of one item on a SERVICE's roadmap (the strategic roadmap's statuses are its own set). Service: Governance. Kept by Clara.

- done: delivered; kept for the record
- in_progress: work serving this item is underway
- planned: the owner intends this; work has not started
- retired: retired in place - overtaken or withdrawn, never deleted

๐Ÿ“–Reuse ladder

The ways a service track serves a project, most preferred first (display order): a grade below the first rung is recorded with the reason the more preferred rungs do not fit (P.01.03.07.27). estate-bound is not a rung (#995); seam-refactor is not an end grade, held while a track must be refactored first (#1033). Service: Blueprint. Kept by Leo.

- as-is: A project uses the estate's existing, running service for this track; nothing is deployed or copied for it. The work the service does for a project is tagged to that project and done by that project's operators, and what it produces may differ with the project's business while the service stays the same (for example the build pipeline or the investment plan). For a client project the service supplies Leo with the questions he asks the client to gather what it needs (#919).
- config-only: The track's logic is already generic, and everything specific to this estate has been pulled out into the instance-config seam. A client project gets it by writing one config file naming its own paths, stores and identities โ€” no code is copied, forked or changed. This is the level the reusability arc moves tracks TO.
- project-extension: The part of a project's requirement that a service does not do, built for that project through the service's extension points, never by changing the service's shared code.
- project-owned-fork: A copy of a service's code that one project owns and pays for, agreed with the client, made only when its customisation outgrows the service's settings and extension points. It is architectural debt.
- project-only-build: Something built new for one project alone because no Carolverse service fits its requirement: the least preferred option on the reuse ladder.
- seam-refactor: Not an end grade (Rulings Repo blueprint #1033): held while a track must be refactored first, until it reads as-is or config-only. The track's logic is generic and worth re-using, but its binding facts โ€” paths, repositories, store addresses, droid identities, model lanes โ€” are still hard-coded. Before any project can have it, those facts must be extracted into per-instance configuration with the estate's current values as the defaults. Handing this track to a project unchanged would point it at Carol's own stores.

๐Ÿ“–Service track status

Lifecycle status of a service track. Service: Cost Center. Kept by Midas.

- live: The record is operating: its droids run and its spend gate answers by budget.
- paused: Deliberately stopped by the switch: droids do not run and the spend gate refuses, but the record stays and can be revived. Paused and the switch move TOGETHER through the one switch door - one fact, one home.
- retired: No longer part of the operating estate. Only an operator decision revives it; a fold into another service ends in deletion with a Trash export (Ninad 2026-09-06), so 'merged' is not a status.

Allowed moves: live to paused, live to retired, paused to live, paused to retired, retired to live.

๐Ÿ“–Kind of a way into the sign-in

What an entry on Heimdall's list of the ways into the sign-in is: never a person (security #609). Service: Security. Kept by Heimdall.

- portal: A page outside the sign-in that leads people to one of its entries, e.g. the Oratorium or the Carol landing page
- app: An app behind the sign-in that sends a signed-out person to sign in
- chat: An agent's chat window that sends a signed-out person to sign in

๐Ÿ“–Status of a way into the sign-in

Whether an entry on Heimdall's list admits sign-ins (security #609, #610). Service: Security. Kept by Heimdall.

- approved: Heimdall or his team approved it: a sign-in reaching it is admitted
- retired: No longer a way in: a sign-in reaching it is refused by name; the entry stays on the list

๐Ÿ“–Slot sign-in kind

Whether a slot's sign-in renews or is a fixed key. Service: Cost Center. Kept by Marco.

- renewing: A plan login: an access pass that runs out and a renewal code that replaces it. Held in full by the keeper alone; callers get a copy that cannot renew.
- fixed_key: A vendor key that does not renew. Held by the keeper alone and handed by the sign-in door for one call.

๐Ÿ“–Slot state

Where a slot stands on the one path every slot enters the estate by. Service: Cost Center. Kept by Marco.

- declared: On record: its key, subscription, model, adapter and sign-in kind are named. Nothing is proven.
- enrolled: Its sign-in is installed with the sign-in keeper (made on the machine, for a renewing one).
- keeper_proven: The keeper proved the sign-in by a real call, and its renewal where it renews.
- login_proven: Every login that will use it reached it through the sign-in door.
- live: Its tracks are registered on it (cookbook 1791) and it carries work.
- suspended: Deliberately stopped by a decision and expected back. Carries no work while it stands.
- retired: Stopped for good. Kept as history, never deleted.

Allowed moves: declared to enrolled, declared to retired, declared to suspended, enrolled to declared, enrolled to keeper_proven, enrolled to retired, enrolled to suspended, keeper_proven to enrolled, keeper_proven to login_proven, keeper_proven to retired, keeper_proven to suspended, live to login_proven, live to retired, live to suspended, login_proven to keeper_proven, login_proven to live, login_proven to retired, login_proven to suspended, suspended to declared, suspended to retired.

๐Ÿ“–What a Blueprint subscription adds in carolverse

What a subscription to Blueprint adds to the open access every registered user holds (operations #593), the subscription's own record -- read by shared.access_approval.subscription_access Service: Operations. Kept by Jarvis.

- external_chat:agt_034: Leo's external chat (Blueprint)
- apps:subscribed: the apps whose access policy admits a signed-in user of carolverse subscribed to the app's service

๐Ÿ“–User kinds of carolverse

The kinds of user Carolverse admits; an access request is recommended and approved as one of these. Recorded by the project's admin and estate operators. Service: Operations. Kept by Jarvis.

- blueprint_subscriber (retired): Blueprint subscriber: a user of carolverse admitted for the Blueprint service. Opens the EXTERNAL chat of Leo (agt_034) and Carol (agt_008), and the apps whose access policy admits a subscribed user of carolverse. Never internal chat, which is for employees. Its access is recorded in user_kind_access.carolverse.blueprint_subscriber.
- client: a verified user of carolverse who has signed its service contract (Rulings Repo operations #603, #605): derived from the contract register by shared.contracts.client_of, never granted by an approval

๐Ÿ“–What a Blueprint subscriber of carolverse opens

Service: Operations. Kept by Jarvis.

- external_chat:agt_034 (retired): Leo's external chat (Blueprint)
- external_chat:agt_008 (retired): Carol's external chat -- RETIRED from this record (operations #593, #608): every registered Carol user holds it as the open access, so a Blueprint subscription never grants it
- apps:subscribed (retired): the apps whose access policy admits a signed-in user of carolverse subscribed to the app's service

๐Ÿ“–Channels a user may ask to be onboarded through

The channels through which a person may ask to become a user of a project. Only these are allowed: an access request names the channel it came through, and one this set does not hold opens nothing (Rulings Repo operations #595). Service: Operations. Kept by Jarvis.

- web_signin: The estate's web sign-in: a person who signs in on the web is registered and their request opens in Jarvis's store.
- whatsapp: Carol's WhatsApp: a person who asks Carol on WhatsApp to become a user.
- web_chat: Carol's web chat: a person who asks Carol in her chat on the web to become a user.

๐Ÿ“–Who approves a user of carolverse

Recorded by the project's admin and estate operators through shared.user_rules Service: Operations. Kept by Jarvis.

- estate_operator: an estate operator of the project approves a user's request
- admin: an admin of the project approves a user's request

๐Ÿ“–Services Carol may recommend a user of carolverse for

Recorded by the project's admin and estate operators through shared.user_rules Service: Operations. Kept by Jarvis.

- blueprint: Carol may recommend a user of carolverse for Blueprint

๐Ÿ“–Work epic status

Whether a work epic -- a group of pursuits driving a larger objective -- is still driving it, reached it, or stopped. Service: Build Initiatives. Kept by Elrond.

- open: Driving its larger objective; an epic serving a blanket objective may stay open for good.
- achieved: Its larger objective is reached: every success criterion is met with its proof.
- abandoned: Stopped for good. Kept as history, never deleted.

Allowed moves: open to abandoned, open to achieved.

๐Ÿ“–Worked time lane

worked time lane Service: Build Initiatives. Kept by Elrond.

- orion_bypass: Orion's bypass lane: an operator's Orion session did the work
- albus_bypass: Albus's bypass lane: his runner did the work

๐Ÿ“–Worked time source

worked time source Service: Build Initiatives. Kept by Elrond.

- worked_turns: worked turns of the session, credited to the initiative it held a claim on (shared evenly across claims held at once)
- only_linked: worked turns of a session that held no claim, credited to the one initiative it was linked to
- attempt_less_idle: no worked turn reached the initiative: its attempt less its idle tail, flagged
- albus_runs: Albus's own bypass run, start to end

๐Ÿ“–Worked tokens basis

worked tokens basis Service: Build Initiatives. Kept by Elrond.

- named: the ledger row names the initiative itself
- worked_time: shared in proportion to the worked seconds the session's time in the period was credited
- claim_held: the session worked no turn in the period: shared evenly over the claims it held across it
- only_linked: the session held no claim in the period: its one linked initiative

๐Ÿ“–Worked tokens grain

worked tokens grain Service: Build Initiatives. Kept by Elrond.

- block: the row is one session's 15-minute block (the laptop marked it turn_timed)
- day: the row carries only its day, so it is placed no finer than the day (flagged)

Source: Data Management ยท Public information reflected here.