FORGE: CO Practitioner Skills

67 skill atoms. 57 drill specs. 25 teaching cases. 25 drill exemplars. Sourced from 232 journal entries of real craft evidence.

FORGE (Foundation for Orchestration, Reasoning, and Generative Engineering) is the canonical practitioner library for the CO ecosystem. It distils the four Terrene Foundation standards into concrete, drillable skills grounded in evidence from real codegen and research workflows.

FORGE is a library, not a course. It provides reusable skill atoms that downstream courses consume and sequence for specific audiences. Courses like Leading AI Transformation, ML Decision-Making, and domain-specific training all draw from FORGE.

Three craft layers

Layer	Atoms	What it covers
Brokerage	18	Operator and governance moves: sync authority chains, variant classification, cross-SDK coordination, ecosystem navigation
Artifact	15	What makes a Claude Code artifact work: rules, hooks, defense-in-depth, progressive disclosure, CLAUDE.md architecture
Practitioner	34	Session-level moves: attention management, intervention timing, institutional memory, research craft (24 COC-layer + 10 COR-layer)

Grounded in four standards

Every atom cites its spec lineage from the Foundation’s standards:

Standard	Role in FORGE	Example atoms
CARE	Why we build the way we build	Dual Plane separation in artifact design, constraint envelope awareness
EATP	How trust flows through systems	Trust posture management, verification gradient in code review
CO	How we orchestrate work	5-layer architecture moves, anti-amnesia patterns, institutional knowledge capture
PACT	How we govern what we build	D/T/R accountability in agent design, operating envelope delegation

What ships with FORGE

Component	Count	Details
Skill atoms	67	Structured as: name, spec lineage, journal evidence, drill, failure mode, related atoms
Drill specs	57	One per COC-layer atom. Beginner (15min), intermediate (30min), advanced (45min)
Drill exemplars	25	Fully expanded with setup, task, model answer, scoring rubric, extensions
Teaching cases	25	Six-section format: situation, trigger, move, outcome, spec connection, discussion questions
Evidence base	232 entries	COC-layer journal entries from loom and terrene codegen workflows

Seven CO applications covered

Application	Atoms	Status
COC (Codegen)	57	Complete. Primary layer. Four red team rounds converged.
COR (Research)	10 new + 18 cross-tagged	Complete. Initial pass, red team converged.
COE (Education)	22 cross-tagged	In scope. Coordinated from downstream courses.
Compliance, Finance, Governance, Learners	Queued	Not yet started.

How courses use FORGE

FORGE imposes no sequence. Courses select, sequence, and deliver:

Select atoms by craft area, application, or spec lineage
Sequence them into a course structure
Use drill specs for practice exercises
Use teaching cases for narrative instruction
When a gap is discovered, the fix enters FORGE first, then courses inherit

Example skill atom

SC-P-001: Identify adjacent-but-disconnected modules as spec conformance gaps

Spec lineage: CO Principle 2 (Institutional Knowledge)
Evidence: 3 journal entries showing missed connections between SDK modules
Drill: Given two modules, identify shared concepts that should be connected
Failure mode: Practitioner treats modules as independent when they share implicit dependencies

Get started

FORGE is open source. Clone the repository and browse the catalog:

git clone https://github.com/terrene-foundation/forge.git
cd forge/catalog

The catalog README provides five indexes: by layer, by craft area, by spec lineage, by modality, and by CO application.

Source: github.com/terrene-foundation/forge
License: Apache 2.0