Shared foundation · Content contract

Front matter is typed content metadata.

One typed registry records author-editable, controlled, and derived fields for route identity, cards, feeds, search, social metadata, machine endpoints, migrations, and publication receipts.

Inspect schemas Open authoring contract Application map

7: route families
30: content types
18: shared fields
6: lifecycle states

identity registry fact

author editable intent

derived named source

receipt exact revision

01 · Schema registry

Shared metadata stays common while each route keeps its own semantics.

Every type has an exact version, required and optional fields, a publication path, and a named registry owner. Deprecated fields remain visible so migration failures cannot disappear behind a successful render.

01 WWW 2 types · 2.0.0 02 Docs 4 types · 2.1.0 03 Benchmarks 5 types · 2.0.0 04 Specs 4 types · 3.0.0 05 Packages 5 types · 2.2.0 06 World 5 types · 2.0.0 07 Learn 5 types · 2.0.0

01 · hara.www

WWW

Narrative pages and product capability claims for the public language site.

Schema: 2.0.0
Owner: WWW content registry
Publication: Markdown + front matter · Hara publication form

Narrative page 2.0.0

Editorial overview with a deliberate argument and proof trail.

Required: contentType · title · summary · authors
Optional: slug · locale · tags · eyebrow · hero · proofRefs

Product capability 2.0.0

A bounded capability claim with registered evidence.

Required: contentType · title · summary · authors · capabilityClaims · proofRefs
Optional: slug · locale · tags · hero

Inspect 22 shared + product fields

Field Requirement Control Source

Schemaschema required Generated from named inputs content type selection

Schema versionschemaVersion required Generated from named inputs schema registry

Content identitycontentId required Registry controlled publication registry

Content typecontentType required Browser editable author selection

Titletitle required Browser editable author

Summarysummary required Browser editable author

Slugslug optional Browser editable author or title default

Canonical URLcanonicalUrl required Generated from named inputs route registry

Authorsauthors required Identity service controlled identity registry

Lifecycle statusstatus required Reviewer controlled publication workflow

Localelocale optional Browser editable author

Tagstags optional Browser editable author + vocabulary registry

Created atcreatedAt required Registry controlled content registry

Updated atupdatedAt required Registry controlled content registry

Exact revisionrevision required Registry controlled deterministic publication pipeline

Publication receiptpublicationReceipt optional Registry controlled publication registry

Provenanceprovenance optional Source registry controlled source registry

Legacy permalinklegacyPermalink deprecated Browser editable legacy front matter

Eyebroweyebrow optional Browser editable author

Hero treatmenthero optional Browser editable author

Capability claimscapabilityClaims optional Browser editable author

Proof referencesproofRefs optional Registry controlled evidence registry

02 · hara.docs

Docs

Guides, references, versions, and executable examples with runtime-aware evidence.

Schema: 2.1.0
Owner: Documentation registry
Publication: Markdown + front matter · Hara documentation form

Guide 2.1.0

Task-oriented path with audience, versions, and optional runnable examples.

Required: contentType · title · summary · authors · audience · versionRange
Optional: slug · locale · tags · prerequisites · outline · runtimeExample

Reference 2.1.0

Canonical API or language reference driven by registered symbols.

Required: contentType · title · summary · authors · versionRange · apiSymbols
Optional: slug · locale · tags · outline

Version note 2.1.0

Version-scoped behaviour and migration guidance.

Required: contentType · title · summary · authors · versionRange
Optional: slug · locale · tags · prerequisites

Live example 2.1.0

Runnable documentation with fenced runtime expectations.

Required: contentType · title · summary · authors · versionRange · runtimeExample
Optional: slug · locale · tags · audience · prerequisites

Inspect 24 shared + product fields

Field Requirement Control Source

Schemaschema required Generated from named inputs content type selection

Schema versionschemaVersion required Generated from named inputs schema registry

Content identitycontentId required Registry controlled publication registry

Content typecontentType required Browser editable author selection

Titletitle required Browser editable author

Summarysummary required Browser editable author

Slugslug optional Browser editable author or title default

Canonical URLcanonicalUrl required Generated from named inputs route registry

Authorsauthors required Identity service controlled identity registry

Lifecycle statusstatus required Reviewer controlled publication workflow

Localelocale optional Browser editable author

Tagstags optional Browser editable author + vocabulary registry

Created atcreatedAt required Registry controlled content registry

Updated atupdatedAt required Registry controlled content registry

Exact revisionrevision required Registry controlled deterministic publication pipeline

Publication receiptpublicationReceipt optional Registry controlled publication registry

Provenanceprovenance optional Source registry controlled source registry

Legacy permalinklegacyPermalink deprecated Browser editable legacy front matter

Audienceaudience required Browser editable author

Prerequisitesprerequisites optional Browser editable author

Version rangeversionRange required Browser editable author

Outlineoutline optional Browser editable author

Live exampleruntimeExample optional Runtime controlled live example registry

API symbolsapiSymbols optional Registry controlled symbol registry

03 · hara.benchmarks

Benchmarks

Reports, workloads, baselines, methodology, and exact evidence without collapsing incomparable results.

Schema: 2.0.0
Owner: Benchmark evidence registry
Publication: Markdown report + front matter · Hara evidence form

Benchmark report 2.0.0

Narrative interpretation of registered workloads and evidence.

Required: contentType · title · summary · authors · question · workloads · baselines · methodology · evidence
Optional: slug · locale · tags · comparability

Workload 2.0.0

Canonical workload identity and implementation revision.

Required: contentType · title · summary · workloads · methodology
Optional: slug · locale · tags · evidence

Baseline 2.0.0

Immutable comparison system and configuration.

Required: contentType · title · summary · baselines
Optional: slug · locale · tags · evidence

Methodology 2.0.0

Reviewed measurement and inclusion contract.

Required: contentType · title · summary · authors · methodology
Optional: slug · locale · tags · comparability

Evidence bundle 2.0.0

Exact samples, environment, and deterministic result receipt.

Required: contentType · title · summary · evidence · workloads · baselines
Optional: slug · locale · tags · comparability

Inspect 24 shared + product fields

Field Requirement Control Source

Schemaschema required Generated from named inputs content type selection

Schema versionschemaVersion required Generated from named inputs schema registry

Content identitycontentId required Registry controlled publication registry

Content typecontentType required Browser editable author selection

Titletitle required Browser editable author

Summarysummary required Browser editable author

Slugslug optional Browser editable author or title default

Canonical URLcanonicalUrl required Generated from named inputs route registry

Authorsauthors required Identity service controlled identity registry

Lifecycle statusstatus required Reviewer controlled publication workflow

Localelocale optional Browser editable author

Tagstags optional Browser editable author + vocabulary registry

Created atcreatedAt required Registry controlled content registry

Updated atupdatedAt required Registry controlled content registry

Exact revisionrevision required Registry controlled deterministic publication pipeline

Publication receiptpublicationReceipt optional Registry controlled publication registry

Provenanceprovenance optional Source registry controlled source registry

Legacy permalinklegacyPermalink deprecated Browser editable legacy front matter

Benchmark questionquestion required Browser editable author

Workloadsworkloads required Registry controlled benchmark registry

Baselinesbaselines required Registry controlled benchmark registry

Methodologymethodology required Reviewer controlled methodology registry

Evidenceevidence required Registry controlled evidence registry

Comparabilitycomparability optional Reviewer controlled benchmark review

04 · hara.specs

Specs

Proposals, versions, conformance, review state, and publication receipts.

Schema: 3.0.0
Owner: Specification registry
Publication: Markdown proposal + front matter · Hara specification form

Proposal 3.0.0

Reviewable change with motivation and registry-assigned identity.

Required: contentType · title · summary · authors · abstract · motivation · specNumber
Optional: slug · locale · tags · compatibility · reviewDecision

Published version 3.0.0

Accepted specification version with durable receipt.

Required: contentType · title · summary · authors · abstract · specNumber · specReceipt
Optional: slug · locale · tags · compatibility · conformance

Conformance record 3.0.0

Checker or implementation evidence against an exact specification.

Required: contentType · title · summary · specNumber · conformance
Optional: slug · locale · tags · reviewDecision

Publication receipt 3.0.0

Registry evidence for an accepted exact version.

Required: contentType · title · summary · specNumber · specReceipt
Optional: slug · locale · tags · reviewDecision

Inspect 25 shared + product fields

Field Requirement Control Source

Schemaschema required Generated from named inputs content type selection

Schema versionschemaVersion required Generated from named inputs schema registry

Content identitycontentId required Registry controlled publication registry

Content typecontentType required Browser editable author selection

Titletitle required Browser editable author

Summarysummary required Browser editable author

Slugslug optional Browser editable author or title default

Canonical URLcanonicalUrl required Generated from named inputs route registry

Authorsauthors required Identity service controlled identity registry

Lifecycle statusstatus required Reviewer controlled publication workflow

Localelocale optional Browser editable author

Tagstags optional Browser editable author + vocabulary registry

Created atcreatedAt required Registry controlled content registry

Updated atupdatedAt required Registry controlled content registry

Exact revisionrevision required Registry controlled deterministic publication pipeline

Publication receiptpublicationReceipt optional Registry controlled publication registry

Provenanceprovenance optional Source registry controlled source registry

Legacy permalinklegacyPermalink deprecated Browser editable legacy front matter

Abstractabstract required Browser editable author

Motivationmotivation required Browser editable author

Compatibility notescompatibility optional Browser editable author

Specification numberspecNumber required Registry controlled specification registry

Review decisionreviewDecision optional Reviewer controlled specification review

Conformanceconformance optional Registry controlled conformance registry

Publication receiptspecReceipt optional Registry controlled specification registry

05 · hara.packages

Packages

Packages, releases, namespaces, maintainers, compatibility, and provenance.

Schema: 2.2.0
Owner: Package and namespace registry
Publication: Markdown package note + front matter · Hara package publication form

Package 2.2.0

Canonical package identity and discovery metadata.

Required: contentType · title · summary · package · namespace · maintainers
Optional: slug · locale · tags · compatibilityMatrix

Release 2.2.0

Immutable package release with artifact evidence.

Required: contentType · title · summary · package · namespace · version · maintainers · artifactDigest
Optional: slug · locale · tags · releaseNotes · migrationNotes · compatibilityMatrix

Namespace 2.2.0

Stewardship scope and publication boundary.

Required: contentType · title · summary · namespace · maintainers
Optional: slug · locale · tags · package

Maintainer record 2.2.0

Identity and delegated package or namespace scope.

Required: contentType · title · summary · namespace · maintainers
Optional: slug · locale · tags · package

Compatibility record 2.2.0

Verified compatibility across exact versions.

Required: contentType · title · summary · package · version · compatibilityMatrix
Optional: slug · locale · tags · artifactDigest

Inspect 26 shared + product fields

Field Requirement Control Source

Schemaschema required Generated from named inputs content type selection

Schema versionschemaVersion required Generated from named inputs schema registry

Content identitycontentId required Registry controlled publication registry

Content typecontentType required Browser editable author selection

Titletitle required Browser editable author

Summarysummary required Browser editable author

Slugslug optional Browser editable author or title default

Canonical URLcanonicalUrl required Generated from named inputs route registry

Authorsauthors required Identity service controlled identity registry

Lifecycle statusstatus required Reviewer controlled publication workflow

Localelocale optional Browser editable author

Tagstags optional Browser editable author + vocabulary registry

Created atcreatedAt required Registry controlled content registry

Updated atupdatedAt required Registry controlled content registry

Exact revisionrevision required Registry controlled deterministic publication pipeline

Publication receiptpublicationReceipt optional Registry controlled publication registry

Provenanceprovenance optional Source registry controlled source registry

Legacy permalinklegacyPermalink deprecated Browser editable legacy front matter

Release notesreleaseNotes optional Browser editable author

Migration notesmigrationNotes optional Browser editable author

Packagepackage required Registry controlled package registry

Namespacenamespace required Registry controlled namespace registry

Versionversion required Registry controlled release registry

Maintainersmaintainers required Identity service controlled namespace registry

CompatibilitycompatibilityMatrix optional Registry controlled compatibility registry

Artifact digestartifactDigest optional Registry controlled package registry

06 · hara.world

World

Articles, clippings, feeds, profiles, source provenance, and accountable bot ownership.

Schema: 2.0.0
Owner: World content and source registries
Publication: Markdown article + front matter · Hara clipping/feed form

Article 2.0.0

Original World article with accountable authorship.

Required: contentType · title · summary · authors · bodyKind
Optional: slug · locale · tags · discussionPrompt · moderation

Clipping 2.0.0

Imported excerpt or link retaining canonical source provenance.

Required: contentType · title · summary · bodyKind · source · provenance
Optional: slug · locale · tags · syndication · discussionPrompt · moderation

Feed registration 2.0.0

Source feed submitted for discovery and review.

Required: contentType · title · summary · authors · source
Optional: slug · locale · tags · syndication · moderation

Contributor profile 2.0.0

Identity-backed contribution, package, namespace, and badge view.

Required: contentType · title · summary · profile
Optional: slug · locale · tags · discussionPrompt

Owned bot 2.0.0

Automation with accountable ownership, policy, and source disclosure.

Required: contentType · title · summary · profile · botOwner · botPolicy
Optional: slug · locale · tags · source · moderation

Inspect 26 shared + product fields

Field Requirement Control Source

Schemaschema required Generated from named inputs content type selection

Schema versionschemaVersion required Generated from named inputs schema registry

Content identitycontentId required Registry controlled publication registry

Content typecontentType required Browser editable author selection

Titletitle required Browser editable author

Summarysummary required Browser editable author

Slugslug optional Browser editable author or title default

Canonical URLcanonicalUrl required Generated from named inputs route registry

Authorsauthors required Identity service controlled identity registry

Lifecycle statusstatus required Reviewer controlled publication workflow

Localelocale optional Browser editable author

Tagstags optional Browser editable author + vocabulary registry

Created atcreatedAt required Registry controlled content registry

Updated atupdatedAt required Registry controlled content registry

Exact revisionrevision required Registry controlled deterministic publication pipeline

Publication receiptpublicationReceipt optional Registry controlled publication registry

Provenanceprovenance optional Source registry controlled source registry

Legacy permalinklegacyPermalink deprecated Browser editable legacy front matter

Body kindbodyKind required Browser editable author

Discussion promptdiscussionPrompt optional Browser editable author

Canonical sourcesource optional Source registry controlled source registry

Syndicationsyndication optional Source registry controlled source registry

Profileprofile optional Identity service controlled identity registry

Bot ownerbotOwner optional Identity service controlled identity registry

Bot policybotPolicy optional Reviewer controlled World policy registry

Moderation statemoderation optional Reviewer controlled World moderation

07 · hara.learn

Learn

Lessons, concepts, prerequisites, exercises, projects, and progress metadata.

Schema: 2.0.0
Owner: Curriculum and progress registries
Publication: Markdown lesson + front matter · Hara curriculum form

Lesson 2.0.0

Guided learning sequence with objectives and optional runnable work.

Required: contentType · title · summary · authors · learningObjectives
Optional: slug · locale · tags · prerequisiteConcepts · estimatedMinutes · runtimeExample · conceptGraph

Concept 2.0.0

Canonical explanation in the curriculum dependency graph.

Required: contentType · title · summary · authors · learningObjectives · conceptGraph
Optional: slug · locale · tags · prerequisiteConcepts

Exercise 2.0.0

Bounded practice task with inspectable checking contract.

Required: contentType · title · summary · authors · learningObjectives · exerciseSpec
Optional: slug · locale · tags · runtimeExample · prerequisiteConcepts

Project 2.0.0

Multi-step useful build with evidence and reflection.

Required: contentType · title · summary · authors · learningObjectives · exerciseSpec
Optional: slug · locale · tags · runtimeExample · prerequisiteConcepts · estimatedMinutes

Progress record 2.0.0

Account-scoped completion evidence against an exact curriculum revision.

Required: contentType · title · summary · progress
Optional: slug · locale · tags · conceptGraph

Inspect 25 shared + product fields

Field Requirement Control Source

Schemaschema required Generated from named inputs content type selection

Schema versionschemaVersion required Generated from named inputs schema registry

Content identitycontentId required Registry controlled publication registry

Content typecontentType required Browser editable author selection

Titletitle required Browser editable author

Summarysummary required Browser editable author

Slugslug optional Browser editable author or title default

Canonical URLcanonicalUrl required Generated from named inputs route registry

Authorsauthors required Identity service controlled identity registry

Lifecycle statusstatus required Reviewer controlled publication workflow

Localelocale optional Browser editable author

Tagstags optional Browser editable author + vocabulary registry

Created atcreatedAt required Registry controlled content registry

Updated atupdatedAt required Registry controlled content registry

Exact revisionrevision required Registry controlled deterministic publication pipeline

Publication receiptpublicationReceipt optional Registry controlled publication registry

Provenanceprovenance optional Source registry controlled source registry

Legacy permalinklegacyPermalink deprecated Browser editable legacy front matter

Learning objectiveslearningObjectives required Browser editable author

Prerequisite conceptsprerequisiteConcepts optional Browser editable author

Estimated minutesestimatedMinutes optional Browser editable author

Exercise specificationexerciseSpec optional Browser editable author

Concept graphconceptGraph optional Registry controlled curriculum registry

Runnable environmentruntimeExample optional Runtime controlled learning runtime registry

Progressprogress optional Registry controlled learner progress registry

02 · Relationship boundaries

Reference the owner of truth. Do not copy its record.

Authors, packages, namespaces, sources, evidence, specifications, and runtimes remain independent registries. Front matter owns relationships and presentation intent—not duplicated authority.

Authors → identitiesmany-to-many

Front matter stores identity references, never copied display names, avatars, roles, or badges.

Content → packagesmany-to-many

Package coordinates, releases, maintainers, and artifact digests remain registry facts.

Packages → namespacesmany-to-one

A content object references stewardship scope instead of duplicating maintainer authority.

Imports → sourcesmany-to-one

Original URL, provider, retrieval time, transformations, and syndication permission form a provenance chain.

Claims → evidencemany-to-many

Visible claims name exact evidence revisions; missing or incomparable evidence remains explicit.

Conformance → specificationsmany-to-one

Conformance always targets an exact specification version and checker contract.

Live examples → runtime receiptsmany-to-many

Source revision, backend, capabilities, expected observations, and execution receipts stay fenced.

03 · Authoring form

Editable intent is visibly separated from controlled fact.

Read-only facts stay selectable and inspectable. They are not disabled inputs. Derived fields name every input, and defaults explain whether they are provisional or durable.

Browser editable

Valid · published Docs guide

Draft editing surface

Content type * Product-specific semantic type chosen from the schema registry. Title * Human-readable title used across the canonical page and derived previews. Summary * Portable description shared by cards, search, feeds, and social metadata. Slug Editable route hint; publication may normalize it without changing content identity. Default: slugify(title). Locale Language and regional context for rendering and discovery. Default: en. Tags Discovery labels resolved against the product vocabulary. Audience * Intended reader experience and task level. Prerequisites Concepts, guides, or packages needed before this content. Version range * Language or package versions for which the content is valid. Outline Stable authored structure used for local navigation.

Server / reviewer controlled

Durable facts

Content identityRegistry controlled Stable identity independent of route, title, or presentation. AuthorsIdentity service controlled Accountable identities referenced rather than copied profile records. Lifecycle statusReviewer controlled Durable state confirmed by the workflow authority; never inferred by the browser. Created atRegistry controlled First durable creation timestamp. Updated atRegistry controlled Timestamp of the exact current revision. Exact revisionRegistry controlled Immutable digest of canonical content and resolved contract facts. Publication receiptRegistry controlled Durable evidence linking actor, revision, status, and regeneration inputs. ProvenanceSource registry controlled Import, syndication, transformation, and original-source chain. Live exampleRuntime controlled Executable source, backend capabilities, expected observations, and exact revision. API symbolsRegistry controlled Canonical symbols referenced by a documentation page.

Generated with provenance

Derived fields

Schemaschema hara.docs/guide Source: content type selection · Inputs: contentType

Schema versionschemaVersion 2.1.0 Source: schema registry · Inputs: contentType + schema registry

Canonical URLcanonicalUrl https://hara-lang.org/docs/guides/durable-work-pipeline Source: route registry · Inputs: contentId + slug + route registry

Valid specimen

docs.guide@2.1.0

Required fields resolve, browser editing stays within author-owned fields, and every durable fact has a named authority.

Invalid + deprecated specimen

specs.proposal@2.4.0

schemaVersion Schema version is required by specs.proposal@3.0.0.
contentId Content identity is required by specs.proposal@3.0.0.
summary Summary is required by specs.proposal@3.0.0.
motivation Motivation is required by specs.proposal@3.0.0.
createdAt Created at is required by specs.proposal@3.0.0.
updatedAt Updated at is required by specs.proposal@3.0.0.
revision Exact revision is required by specs.proposal@3.0.0.
legacyPermalink Legacy permalink is deprecated; use canonicalUrl.

Migrated specimen

packages.release@2.2.0

Deterministic migration receipt receipt:migration:mig-5501 links input and output revisions.

Input: sha256:legacy-2f19
Output: sha256:0cc8d46f

04 · Representations

One canonical object. Multiple inspectable authoring paths.

YAML, JSON, and Hara forms are representations of the same resolved contract. Markdown and Hara publication paths differ in authoring syntax, not content identity, validation, or receipts.

YAML front mattertext/yaml

audience:
  - application-developer
authors:
  - "identity:github:hoebat"
canonicalUrl: "https://hara-lang.org/docs/guides/durable-work-pipeline"
contentId: "hara:docs:guide:durable-work-pipeline"
contentType: docs.guide
createdAt: "2026-08-12T04:10:00Z"
locale: en-AU
outline:
  - model
  - steps
  - receipts
prerequisites:
  - learn.concept/work-algebra
publicationReceipt: "receipt:docs:pub-1098"
revision: "sha256:72a194a3"
schema: hara.docs/guide
schemaVersion: 2.1.0
slug: durable-work-pipeline
status: published
summary: "Model replayable work, checkpointed steps, and explicit capability boundaries."
tags:
  - work
  - durability
  - runtime
title: Build a durable work pipeline
updatedAt: "2026-08-19T12:44:00Z"
versionRange: >=1.8 <2.0

Canonical JSONapplication/json

{
  "audience": [
    "application-developer"
  ],
  "authors": [
    "identity:github:hoebat"
  ],
  "canonicalUrl": "https://hara-lang.org/docs/guides/durable-work-pipeline",
  "contentId": "hara:docs:guide:durable-work-pipeline",
  "contentType": "docs.guide",
  "createdAt": "2026-08-12T04:10:00Z",
  "locale": "en-AU",
  "outline": [
    "model",
    "steps",
    "receipts"
  ],
  "prerequisites": [
    "learn.concept/work-algebra"
  ],
  "publicationReceipt": "receipt:docs:pub-1098",
  "revision": "sha256:72a194a3",
  "schema": "hara.docs/guide",
  "schemaVersion": "2.1.0",
  "slug": "durable-work-pipeline",
  "status": "published",
  "summary": "Model replayable work, checkpointed steps, and explicit capability boundaries.",
  "tags": [
    "work",
    "durability",
    "runtime"
  ],
  "title": "Build a durable work pipeline",
  "updatedAt": "2026-08-19T12:44:00Z",
  "versionRange": ">=1.8 <2.0"
}

Hara formapplication/hara

(content/frontmatter
  {:audience ["application-developer"] :authors ["identity:github:hoebat"] :canonicalUrl "https://hara-lang.org/docs/guides/durable-work-pipeline" :contentId "hara:docs:guide:durable-work-pipeline" :contentType "docs.guide" :createdAt "2026-08-12T04:10:00Z" :locale "en-AU" :outline ["model" "steps" "receipts"] :prerequisites ["learn.concept/work-algebra"] :publicationReceipt "receipt:docs:pub-1098" :revision "sha256:72a194a3" :schema "hara.docs/guide" :schemaVersion "2.1.0" :slug "durable-work-pipeline" :status "published" :summary "Model replayable work, checkpointed steps, and explicit capability boundaries." :tags ["work" "durability" "runtime"] :title "Build a durable work pipeline" :updatedAt "2026-08-19T12:44:00Z" :versionRange ">=1.8 <2.0"})

Markdown publication path.md

---
audience:
  - application-developer
authors:
  - "identity:github:hoebat"
canonicalUrl: "https://hara-lang.org/docs/guides/durable-work-pipeline"
contentId: "hara:docs:guide:durable-work-pipeline"
contentType: docs.guide
createdAt: "2026-08-12T04:10:00Z"
locale: en-AU
outline:
  - model\n…

Hara publication path.hal

(content/publish
  {:frontmatter {:audience ["application-developer"] :authors ["identity:github:hoebat"] :canonicalUrl "https://hara-lang.org/docs/guides/durable-work-pipeline" :contentId "hara:docs:guide:durable-work-pipeline" :contentType "docs.guide" :createdAt "2026-08-12T04:10:00Z" :locale "en-AU" :outline ["model" "steps" "receipts"] :prerequisites ["learn.concept/work-algebra"] :publicationReceipt "receipt:docs:pub-1098" :revision "sha256:72a194a3" :schema "hara.docs/guide" :schemaVersion "2.1.0" :slug "durable-work-pipeline" :status "published" :summary "Model replayable work, checkpointed steps, and explicit capability boundaries." :tags ["work" "durability" "runtime"] :title "Build a durable work pipeline" :updatedAt "2026-08-19T12:44:00Z" :versionRange ">=1.8 <2.0"}
   :body (document/body ...)})

05 · Metadata-driven preview

The same facts must visibly drive every surface.

Route, card, feed, search, social, and machine previews expose their input facts. Light, dark, and narrow frames demonstrate presentation parity without changing the canonical object.

Canonical route /docs/guides/durable-work-pipeline hara:docs:guide:durable-work-pipeline

Card · light1280

Docs

Build a durable work pipeline

Model replayable work, checkpointed steps, and explicit capability boundaries.

Feed · dark1280

A useful discussion of algebraic effects

A clipped external article retained at its canonical source with a World discussion context.

https://example.org/algebraic-effects

reviewed

Search · narrow320

docs.guide

Build a durable work pipeline

Model replayable work, checkpointed steps, and explicit capability boundaries.

sha256:72a194a3

Machine endpointapplication/ld+json

{
  "@context": "https://hara-lang.org/content/v2",
  "@id": "hara:docs:guide:durable-work-pipeline",
  "@type": "docs.guide",
  "url": "https://hara-lang.org/docs/guides/durable-work-pipeline",
  "name": "Build a durable work pipeline",
  "description": "Model replayable work, checkpointed steps, and explicit capability boundaries.",
  "revision": "sha256:72a194a3"
}

06 · Lifecycle and receipts

Status changes are durable relations, not coloured labels.

Each transition names the actor and evidence boundary. Superseded and withdrawn content keeps history, while exact revisions and deterministic regeneration receipts make every published surface reproducible.

01

Draft
Editable content has no public identity and may be discarded.
Actor
Author
Evidence
Local or account-scoped
02

Proposed
The exact submitted revision is fenced while review remains pending.
Actor
Author + registry
Evidence
Submission receipt
03

Reviewed
Reviewer identity, decision, comments, and source revision are inspectable.
Actor
Reviewer
Evidence
Review receipt
04

Published
Canonical identity, route, exact revision, and machine representation are durable.
Actor
Publisher
Evidence
Publication receipt
05

Superseded
History remains available and points to the replacing revision or object.
Actor
Registry
Evidence
Replacement relation
06

Withdrawn
The object is not current, but its identity, reason, and receipts remain inspectable.
Actor
Owner or authority
Evidence
Withdrawal receipt

Exact publication receipt

`receipt:docs:pub-1098`

Content: hara:docs:guide:durable-work-pipeline
Revision: sha256:72a194a3
Schema: hara.docs/guide@2.1.0
Actor: identity:github:hoebat
Generator: content.publish@2.1.0

Deterministic regeneration

Same inputs → same revision

01Resolve schema and registry references.
02Canonicalize authored and controlled facts.
03Generate route and machine representations.
04Digest exact bytes and issue receipt.

Migration notice

hara.packages/release@1.4.0 → hara.packages/release@2.2.0

owner → maintainers identity references
packageCoordinate → package registry reference
permalink → canonicalUrl derived from registry identity

Receiptreceipt:migration:mig-5501

07 · Imported and syndicated provenance

A clipping never pretends to be the original.

Source identity, retrieval, transformations, digests, permissions, and import receipts remain visible. World owns discussion context while the canonical article remains at its original destination.

Imported specimenworld.clipping

A useful discussion of algebraic effects

A clipped external article retained at its canonical source with a World discussion context.

https://example.org/algebraic-effects

01
Original source
web · sha256:9dd2e7b4
02
Retrieval
2026-08-18T08:11:42Z
03
Transformations
readability-extract · excerpt-240-words
04
Import receipt
receipt:source:imp-592
05
World discussion object
hara:world:clipping:gw-4821 · sha256:84cb31e8

08 · Ownership and adoption

Applications consume the contract; they do not fork it.

Shared field semantics and control boundaries stay here. Each application owns realistic domain composition, business rules, and application-specific workflows while linking back to the exact content families it consumes.

Shared content contract owns

Portable semantic boundaries

field identity, requirement, version, control, and source
lifecycle vocabulary and immutable receipt shape
canonical identity, route derivation, migration, and provenance rules
representation and preview equivalence

Application owns

Domain policy and composition

who may submit, review, publish, moderate, or withdraw
ranking, curriculum, compatibility, and conformance business rules
page information architecture and workflow-specific evidence
downstream storage and registry implementation

Catalogue-only annotation

Review framing, never production API

field callouts, device frames, relationship diagrams, and specimen ledgers
invalid, deprecated, migrated, and imported comparison arrangements
reference labels that explain ownership and responsive behaviour

WWW / Docs / Benchmarks#38

wwwdocsbenchmarks

Narrative, guide, reference, live-example, report, workload, methodology, and evidence metadata.

Playground#39

docslearn

Live-example identity, source revision, runtime capability, shareable route, and execution receipt references.

Specs#40

specs

Proposal, version, review, conformance, status, and publication-receipt metadata.

Packages#41

packages

Package, release, namespace, maintainer, compatibility, and artifact provenance metadata.

World#42

world

Article, clipping, feed, profile, accountable bot, source, syndication, and moderation metadata.

Learn#43

learn

Lesson, concept, prerequisite, exercise, project, runtime, and progress metadata.