Capability Commons

What it is

Most people do not need more information. They need clearer paths from understanding to action. The internet has more information than anyone could consume. The problem is not content — it is structure. Knowledge exists, but it is not organized for a beginner who needs to act, does not know the vocabulary, and cannot afford to get it wrong.

Capability Commons takes knowledge that is normally trapped inside trades, institutions, guilds, paywalls, jargon, and credential barriers, and converts it into structured, searchable, teachable objects that anyone can use.

AI is not the product. AI is the compiler. It takes source material and helps transform it into structured, plain-language capability objects. Human review and field testing decide what becomes canon.

Three interlocking graphs

The system is not a document library. It is three graphs working together:

• Concept graph — what things mean and how ideas relate. "What is thermal mass?" "How does soil pH affect nutrient availability?"
• Skill graph — what people can do, in what order, with what prerequisites. "What can I do next?" "What must I know first?"
• Deployment graph — where, when, and under what constraints something is useful. "Does this work in my apartment?" "What's the low-budget version?"

That combination is what lowers the barrier to entry. Not just explanation, but explanation tied to action and context.

Knowledge object model

Every node uses the same structure: a typed knowledge object with a canonical title, plain-language explanation, structured payload, prerequisite logic, context-aware facets, and durable output artifacts.

Five-format publishing rule

Every core topic exists in five forms:

1. Hook — a compelling 1–2 sentence pitch for why this matters
2. Primer — plain-language background explanation
3. Guide — step-by-step practical instructions
4. Reference — specs, formulas, diagrams, checklists
5. Teach-forward kit — how to pass it on (3-minute version, 10-minute outline, discussion prompts)

Entry model

People start with immediate needs and expand outward through concentric rings:

1. Stay functional — verify information, store water, keep lights running, maintain heat
2. Repair and maintain — hand tools, patching, sealing, diagnosing common failures
3. Produce — gardening, preservation, rainwater, solar basics, local resource mapping
4. Coordinate — shared inventories, mutual aid, tool libraries, communication plans
5. Steward and transmit — documentation, teaching methods, archives, offline kits

Every module includes a plain-language version and zero-jargon glossary, cheap / better / best paths, renter / homeowner / rural / urban adaptation, what you can do with minimal tools, common mistakes, how to verify your work, and what to learn next.

Why now

Practical competence has become fragmented, gated, outsourced, or trapped behind institutions, jargon, and disappearing local memory.

The point of Capability Commons is not nostalgia. It is public capacity. The metric is not attention — it is replicated competence: modules completed by real people, tasks performed in the physical world, people who teach another person what they learned, local variants documented, offline kits distributed.

What is live now

The platform is being built in public. The following is operational.

Architecture

Capability Commons is built on the Agentic Data Lite architecture — a trimmed version of the enterprise AgenticData stack focused on versioned knowledge objects, typed edges, evidence provenance, and retrieval planning.

Stewardship

Capability Commons is founded and stewarded by Jason St George.

The public initiative sits under a larger body of work on truth, coordination, verification, and resilient systems under adversarial conditions. The technical substrate — Agentic Data Lite — provides versioned knowledge objects, typed edges with provenance, evidence-pack assembly, contradiction workflows, and retrieval planning for long-horizon maintenance.

Lifecycle states for all objects: DRAFT → IN_REVIEW → REVIEWED → VERIFIED → PUBLISHED → DEPRECATED. Transparent version history, editorial standards, and subject-matter review. No black-box canonical truth claims.