Policy structured like code. Written like law. Read like a manual.
The Clearline Framework is a structured policy library organized as ten Titles. Each Title contains numbered sections and lettered subsections. Authority, scope, definitions, standards, and procedures are explicit. The result is a corpus that practitioners can navigate and machines can index.
What the framework contains
Ten Titles cover the operating surface of a delivery PMO. Titles are licensed as a complete set. Customers replace placeholder content with their own under controlled amendment procedures.
| Title | Subject | Scope |
|---|---|---|
| Title 1 | Foundation | Governs the Framework itself: what it is, who holds authority over it, how it changes, how its records are kept, how it is cited, and how its meaning is settled. |
| Title 2 | Roles and Responsibilities | |
| Title 3 | Delivery System and Intake Standards | sec.9 Portfolio Governance: how investment is authorized, prioritized, and rebalanced at the portfolio level, and how an authorized investment hands off to tier classification. |
| Title 4 | Financial Treatment | sec.2 Capital and Expense Treatment: the evidence the PMO supplies so that the licensee's finance function can determine whether project cost is capitalized or expensed. |
| Title 5 | Project Delivery Standards | Governs project delivery: the delivery tier model, tier classification, the governance each tier carries, classification integrity, and the delivery lifecycle from planning through closeout. |
| Title 6 | Risk, Issue, Decision, Action, and Change Management | |
| Title 7 | Reporting and Data Quality | |
| Title 8 | Governance | Governs the layers that apply the Framework: change control for practices and tooling, Framework Records in automated systems, AI governance, and audit. |
| Title 9 | Program Management Standards | |
| Title 10 | Agile Development Team Standards |
Format and citation
Every section follows the same skeleton: Authority, Purpose, Scope, Definitions, Policy, Standards, Procedures, Roles, Compliance, Exceptions, Amendments, Cross References. Citations follow a deterministic pattern [Title] [FW] sec.[section]([subsection])([item]) so that any clause can be referenced unambiguously by a person, a downstream document, or a model.
1 [FW] sec.3(5)(d) — Title 1, section 3, subsection 5, item d.
Why legal-document structure
Legal codes are the most rigorously structured policy artifacts in human use. They are designed for citation, amendment, and retrieval at scale across decades. PMO standards have the same requirements and almost never get the same treatment. Clearline borrows the structure because the structure works.
The format also produces a corpus that is exceptionally retrievable. Numbered headings, consistent section types, and explicit definitions are exactly what an agent needs to ground an answer. The framework was designed for this from the first draft.
How customers adopt it
- License the framework structure with placeholder content tagged for substitution
- Map your existing standards to the Title and section structure
- Run a controlled amendment process — every change carries a discrete history entry
- Publish the framework to your governance repository under controlled change procedures
- Connect the framework to the PMO Delivery Desk and the Agent
The framework is the foundation. Everything else is downstream.
Without a structured corpus, the Delivery Desk is decoration and the agent is a search engine.
See a sample section