BLOG

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-canonic.github.io/
web_surface: https://hadleylab-canonic.github.io/SERVICES/BLOG/
web_app:     https://hadleylab-canonic.github.io/BLOGS/
magic:       magic://hadleylab-canonic.github.io/SERVICES/BLOG/

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 DEXTER 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