Axiom

BLOG is the editorial voice of governed infrastructure. Every post is a PROOF artifact — sourced, compiled, and surfaced. The blog publishes what the system proves.

Constraints

MUST:     Source every claim from governed scopes (papers, services, ledger events, transcript IDFs)
MUST:     Declare front matter per post (title, date, scope, tags)
MUST:     Compile through MAGIC pipeline — no hand-published HTML
MUST:     Emit SHOP-safe projections for public surface
MUST:     Ledger every publish event (author, date, scope, commit hash)
MUST:     Every child instance at BLOGS/ inherits these constraints
MUST:     Validate all citation codes ([X-n], [W-n], [B-n], etc.) against BIBLIOGRAPHY.md before publish
MUST:     Render citation codes as hyperlinked references on WEB surface — no raw [X-n] in published HTML
MUST:     Citation hyperlinks open source in new tab (target="_blank") — never steal focus from the reading surface
MUST NOT: Publish private or VAULT-gated content on public surface
MUST NOT: Publish unsourced claims — every assertion traces to evidence
MUST NOT: Hand-author compiled outputs
MUST NOT: Bypass build pipeline — governance compiles, not hand-edit
MUST NOT: Pass raw citation codes to published surface — resolve to source or fail
MUST NOT: Double-title names (Dr. Firstname Lastname, MD) — compiler-detectable, regex gate
MUST NOT: Expose governance dimension codes, bit weights, or bitmask formulas in reader-facing prose — patented IP

Capabilities

CLAIM_SOURCE, MAGIC_COMPILE, POST_PUBLISH, PROOF_EMIT

COVERAGE: 255/255

SPEC

Purpose

BLOG is the publishing API for governed editorial content.

Every blog post is a PROOF artifact — authored in markdown, compiled through the MAGIC pipeline, and surfaced on the governed frontend. BLOG is a SHOP-gated publishing lane: only SHOP-safe projections reach the public surface.

Structure

Leaf SERVICE scope. No governed child scopes. Blog content lives in {USER}/BLOGS/ (instance scope, SHOP.md projection). Instance follows the Instance Pattern at {USER}/BLOGS/.

Required closure artifacts per scope: CANON.md, README.md, BLOG.md, VOCAB.md, ROADMAP.md, COVERAGE.md, LEARNING.md.

Learning lane per governed scope: LEARNING.md at the scope root is terminal and SHALL NOT nest further LEARNING/.

Routes

web_docs:    https://hadleylab.org/
web_surface: https://hadleylab.org/SERVICES/BLOG/
web_app:     https://hadleylab.org/BLOGS/
magic:       magic://hadleylab.org/SERVICES/BLOG/

Surface

layout:   post                              <- _layouts/post.html (editorial format)
body:     post-page                         <- CSS class, single-col prose
view:     gov | web                          <- GOV contract + WEB prose (no PDF)

Publishing Contract

1. Author writes {POST}.md in {USER}/BLOGS/
2. Front matter declares: title, date, scope, tags
3. Build pipeline compiles to Jekyll-compatible HTML
4. SHOP.md projection emits public-safe metadata (title, date, excerpt)
5. VAULT.md projection emits full content (auth-gated if PRIVATE)
6. Published artifacts are deterministic — same source = same output

Ecosystem Connectivity

1. Upstream: SERVICES governance contracts and hadleylab-canonic scope inheritance.
2. Runtime: Jekyll compilation via remote_theme — governed markdown to static HTML.
3. Frontend: BLOGS/ surface compiled to governed SPA route. SHOP-safe excerpts in catalog.
4. Ledger plane: publish events ledgered (author, date, scope, commit hash).

Pages

Default: Overview.

Instance Pattern

{USER}/BLOGS/
  BLOGS.md       <- instance spec
  CANON.md       <- scope governance
  SHOP.md        <- public projection
  COVERAGE.md    <- compliance
  LEARNING.md    <- learning trail
  README.md      <- scope readme
  ROADMAP.md     <- scope roadmap
  VOCAB.md       <- scope vocabulary

INTEL

Publishing Landscape

BLOG is the editorial lane — shorter-form, opinion-backed-by-evidence, public by default.

Content Pipeline

Editorial Standards

Writing Conventions

• MD/PhD (slash, not comma). Penn convention.
• Penn (not UPenn).
• Titles: first mention = Full Name, Credentials (Marisa Nimrod, MD, MPH). Subsequent = Dr. Surname (Dr. Nimrod). Never both.
• Flowing human prose with conjunctions and subordinate clauses. No staccato sentence fragments.
• Minimize em dashes. Prefer commas, colons, semicolons, parentheses, or subordinate clauses.
• IP narration: keep file names and question mappings. Remove governance dimension codes, bit weights, and bitmask formulas from reader-facing prose. The codes are patented IP. The files are public.

Instance Coverage

Cross-Scope Connections

Risk Assessment

Test

LEARNING

ROADMAP

Now

Next

Later

VOCAB

INHERITANCE CHAIN

SERVICES

SERVICES compose primitives — INTEL + CHAT + COIN. Every service governed. Every scope discovered.

MUST:     Maintain TRIAD integrity (CANON.md + VOCAB.md + README.md)
MUST:     Treat SPEC as scope identity (`{SCOPE}` directory), not as a file
MUST:     Every SERVICE scope include ROADMAP.md, COVERAGE.md, LEARNING.md, and `{SCOPE}.md` as governed content surfaces
MUST:     Discover SERVICE scopes from filesystem only (no manual catalog)
MUST:     Keep http:// and magic:// on the same namespace (transport differs, scope path matches)
MUST:     CANON.md = axiom + universal constraints (no service names, no paths, no implementation)
MUST:     README.md = how to run the CANON (nothing else)
MUST:     {SCOPE}.md = SPEC — the interface (purpose, routes, projections, ecosystem)
MUST:     SHOP.md = public projection file (per scope, filesystem-discoverable)
MUST:     VAULT.md = private projection file (per scope, filesystem-discoverable)
MUST:     Runtime implementation remains under ~/.canonic; this workspace is governance-first
MUST NOT: Hardcode service names in CANON constraints (law speaks universals)
MUST NOT: Define ungoverned terms outside VOCAB.md
MUST NOT: Treat `{SCOPE}.md` as SPEC identity
MUST NOT: Move architecture/lifecycle into README
MUST NOT: Leak private projections to public surfaces
MUST NOT: Maintain duplicate mapping tables outside generated manifest outputs
MUST NOT: Add runtime jargon to governance contracts
MUST:     Ledger-consuming services declare source ledgers, scope filters, and closure gates
MUST:     Learning governance remains live — closure claims require fresh DISCOVER → GENERATE → RELINK evidence

hadleylab-canonic

HADLEYLAB ships software. Every app, book, paper, deal, and patent is PROOF that MAGIC works. COIN = WORK. LEARNING = COMPUTE.

MUST:     Every app, book, paper, deal, or patent is evidence of MAGIC
MUST:     All scopes inherit canonic-canonic/CANONIC.md governance
MUST:     All users governed under USERS/ via SERVICES/USER
MUST:     Cross-index INTEL across users (INTEL.md)
MUST:     Shared events propagate to ALL affected user dashboards
MUST:     Maintain governance workspace purity (.md files only)
MUST:     Ledger all COIN (validated work) through MAGIC 255
MUST:     Compile all INTEL from governed sources
MUST:     Keep frontend/runtime implementation under ~/.canonic (hidden runtime)
MUST:     Surface governed TALK, Library, and SERVICES scopes (no orphan content)
MUST:     Derive nav labels from governed scope names (no hardcoded strings)
MUST NOT: Publish without governance (CANON.md required)
MUST NOT: Duplicate primitives — compose from INTEL, CHAT, COIN
MUST NOT: Silo intelligence inside a single user when multiple are affected
MUST NOT: Expose VAULT contents outside NDA scope
MUST NOT: Store runtime artifacts in governance workspace

canonic-canonic

SPEC is governance. `canonic-canonic/` is the spec root.

MUST:     Keep this repo governance-only (.md/.pdf)
MUST:     Publish workspace mapping in CANONIC.git (no hardcoded repo lists)
MUST:     Preserve three primary lanes: FOUNDATION, INDUSTRIES, MAGIC
MUST NOT: Commit runtime artifacts here (runtime belongs in ~/.canonic/)
MUST:     Sell MAGIC tiers — the product, not the proof (proof is hadleylab-canonic)
MUST NOT: Embed beta-test app URLs in platform page content