24 domains
Seven Hardware, six Operating System and eleven Applications domains remain unchanged and are not collapsed into a composite.
Capability Commons · Planned next
Improve the knowledge without losing trust.
The Capability Commons is the planned collaborative layer around Titan's living capability atlas. When its intake is explicitly activated, readers, researchers, practitioners and people with lived experience will be able to propose capabilities, submit evidence and challenge claims. Eligible submissions will then feed the Titan Research & Governance Lab’s master register; they will not write directly to the book, become a vote or promote themselves. Public intake remains closed.
Candidate framework within the Commons
A new lens, not a new score.
The Multi-Locus Capability Architecture (MLCA) v0.2 does not expand the frozen Core or promote a new operational module. It separates who or what bears a capability claim from how performance is produced, then tracks outcomes, burden and legitimacy without collapsing them into one index.
16 modules
The seven-family Capability Standard remains separate and unchanged.
Candidate v0.2
One read-only research framework inside the planned Commons, with no assessment, vote, recommendation or automatic promotion.
Universal index
No global human, institutional or societal worth score is permitted.
Relationship to the internal Lab: the Commons is the planned public participation doorway; the Titan Research & Governance Lab is the subordinate programme that preserves, reviews and routes admitted research objects through one register, one archive and one promotion process. They are not competing products.
Non-compensatory rule: safety, consent, accessibility, privacy, rights and legitimacy cannot be averaged away by strong performance.
Orthogonal axis 01
Capability Locus Stack
The locus is the bounded bearer of the claim. It is not a hierarchy of human worth. Every claim names one primary locus and keeps supports, nested actors and joint production visible.
Individual
One person is the bounded bearer; supports and joint production remain visible.
Relational unit
A dyad, household or care unit whose function depends on patterned interaction.
Team
A crew, cohort, committee or community of practice with a shared function.
Organisation
A legally, administratively or operationally bounded organisation with continuity.
Inter-organisational network
A persistent network with declared participation, coordination and shared function.
Institutional system
A bounded system of organisations, rules, authority, incentives and infrastructure.
Bounded societal system
A public system bounded by jurisdiction, population, function and timeframe.
Execution configuration is separate: human-only, multi-human, human–tool, human–AI, human–robot, human-governed automation, human-governed multi-agent and mixed sociotechnical configurations describe how performance is produced.
Translation model
From need to legitimate outcome.
Information is not capability, and demonstrated performance is not automatically a worthwhile outcome. The translation spine makes each failure point inspectable.
- 01Need or opportunity
- 02Discovery
- 03Evidence
- 04Governed knowledge
- 05Usable representation
- 06Capability formation
- 07Capability deployment
- 08Sustained performance
- 09Functional outcomes
- 10Flourishing alignment
This is an explanatory spine, not a compulsory one-way causal sequence. Outcomes feed back into evidence and governed knowledge; judgement, decision and action are deployment functions.
Front-door diagnostic
The Capability Gap is a profile.
A gap is the uncertainty-aware difference between the performance required by a declared outcome and the performance currently demonstrated by the relevant locus under actual conditions. It is never one universal number.
- KNOWLEDGE_GAP
- Required information is absent or unavailable.
- UNDERSTANDING_GAP
- Information exists but is not comprehended or usable.
- ACQUISITION_GAP
- The capability has not been learned or formed.
- DEPLOYMENT_GAP
- Capability exists but is not selected or used when needed.
- JUDGEMENT_GAP
- Options are understood but selection is unreliable for the declared task.
- COORDINATION_GAP
- Capable actors cannot combine action reliably.
- TRANSFER_GAP
- Performance fails outside the training or source context.
- MAINTENANCE_GAP
- Capability or enabling conditions have decayed.
- RESOURCE_GAP
- Tools, time, money, staffing or infrastructure are absent.
- ACCESS_GAP
- The route, environment or interface excludes intended users.
- SYSTEM_GAP
- Rules, incentives or processes prevent the required performance.
- LEGITIMACY_GAP
- Consent, rights, jurisdiction or authority is absent.
- OUTCOME_GAP
- Performance occurs but does not produce the intended result.
Capability by Design
Change the right part of the system.
The question is not automatically “How do we train the person harder?” Select the lowest-burden safe and legitimate change to the person, task, tool, environment, workflow or institution.
- ACQUIRE
- TRAIN
- SUPPORT
- AUGMENT
- SUBSTITUTE
- REDESIGN_CONTEXT
- REDESIGN_INSTITUTION
- MAINTAIN
- RECOVER
- RETIRE
Performance is not automatically valuable.
- Whose outcome is being pursued?
- Who selected it and with what authority?
- What is the minimum meaningful benefit?
- What burdens and opportunity costs accompany it?
- Who benefits, who is affected and who bears risk?
- What protected outcomes must not deteriorate?
- Could context or institutional redesign achieve it more safely?
- Are appeal, withdrawal and the right to stop preserved?
Plural, self-directed and non-scoring.
- Does the outcome still matter after novelty fades?
- Has it increased or reduced autonomy?
- Has it created dependency or hidden labour?
- Has it strengthened dignity, relationships and belonging?
- Are burdens falling on people who did not choose the objective?
- Would stopping be a legitimate success?
Governance lifecycle
Admission is not promotion.
- ObservationRecorded without Candidate or operational standing.
- Lab admissionAn eligible object receives a governed identity and route; admission alone grants no Candidate or operational standing.
- Observatory or CandidateEvidence gathering and bounded testing remain separate lanes. MLCA v0.2 is Candidate work.
- ExperimentalUnder a separately authorised declared protocol; not operational guidance.
- OperationalExplicitly approved for bounded use under continuing review.
- MaintainedEvidence, safeguards and dependencies remain current.
- SuspendedUse pauses while a material problem is investigated.
- Retired or rejectedWithdrawn while provenance and decision history remain preserved.
Current state: MLCA v0.2 is Candidate research. The institutional pilot has not been executed, and no pre-pilot execution gate has been evidenced as complete (0 of 20). This page has no assessment, vote, public submission, migration, recommendation, promotion or write path.
Public research boundary
Public reading now. Governed participation next.
The site and book are available as a public read-only preview. Public contribution intake remains closed while privacy, moderation, accessibility, staffing and review safeguards are completed. Until activation, nothing submitted elsewhere becomes a Commons proposal, enters the Lab register or changes Titan.