№ 04 · PROCESSREC / public-content-model
candidate

public content model

The typed Astro content layer for public records, evidence, operations, decisions, relations, matters, notes, and docs.

Astro collection config, typed record helpers, public content report, and current content entries.

  • content model
  • public boundary
  • collections
  • validation
Domaincontent-platformVersion0.1.0Updated2026-07-01MaintainerazwerksProofpartial

Overview

01

What it is

The typed Astro content layer for public records, evidence, operations, decisions, relations, matters, notes, and docs.

Canonical facts

Domain
content-platform
Version
0.1.0
Updated
2026-07-01
Maintainer
azwerks
Proof
partial
  • The model is active in the current site, but final search, feed, and sitemap integration are not complete.
  • The four intake-derived project records are now public candidate records; proof upgrades and asset review remain unresolved.

How the record thinks

02

Key decisions

01

Decision

Where should public register data live?

ChosenUse Astro content collections with typed helper modules for public filtering and record assembly.

Collections provide schema validation, source files, and a durable boundary between content and page composition.

Alternatives considered

  • Continue page-local fixtures — Would keep fixture data scattered through public routes.
  • Use a remote CMS now — Would add operational complexity before the public model is stable.

Consequences accepted

  • Public pages must use async helper functions.
  • Invalid enum values and missing required fields fail during content sync or build.
Recorded
2026-07-01
Source
content model prompt

Lineage

03

History

Operations

Content model

  1. Content model2026-07-01

    current

    Introduce typed content collections

    Created content collections for records and related register entities.

    Intent
    Replace page-local fixture data with validated public-safe content.
    Action
    Added Astro collection schemas, JSON content entries, and public helper modules.
    Result
    Public pages can read records through centralized helpers.

    The data set is intentionally small and still needs search, feed, and editorial workflow coverage.

  2. Content model2026-07-01

    current

    Centralize public boundary

    Moved public filtering into shared content helpers and kept non-public records out of route generation.

    Intent
    Ensure public pages render only records with `visibility: public`.
    Action
    Added public helper functions for records, evidence, operations, decisions, relations, matters, docs, notes, route entries, result records, and command records.
    Result
    Public routes read through centralized helpers instead of scattered page-level filters.

    Future search, sitemap, feed, and metadata generation must keep using the same boundary.

How do you know?

04

Evidence

04

Public content model report

reviewed

Documents the content collection architecture, public helpers, validation behavior, and page integration.

File:
docs/azwerks-portfolio-public-content-model-report-v1.0.md
Scope:
content platform

Search and feed integration are documented as deferred work.

Astro content collection config

reviewed

Defines schemas for records, evidence, operations, decisions, relations, matters, notes, and docs.

File:
src/content.config.ts
State:
source-cited

Record type contracts

reviewed

Defines public record, evidence, operation, decision, relation, matter, note, and doc types.

File:
src/types/records.ts
State:
source-cited

Public record helper module

reviewed

Centralizes public filtering, route generation, entity lookup, and validation behavior.

File:
src/lib/records.ts
State:
source-cited

Unresolved

05

Open matters

02

Matter ledger

Open matters stay visible and separate from decisions.

Open content matters

  1. Open questionmat-content-model-search-indexes2026-07-01

    open

    Wire search, command, sitemap, and feed inputs

    Public helpers exist, but future search, command, sitemap, metadata, and feed generation must keep using the same visibility boundary.

    Position
    Add static search and command indexes in the next prompt using only public helper output.

    The current model does not yet prove every future index surface.

  2. Open questionmat-content-model-evidence-validation2026-07-01

    open

    Expand evidence validation coverage

    Evidence file paths are checked for configured source roots, but future external artifact, asset, and screenshot approvals need a stricter workflow.

    Position
    Keep current evidence source-backed and defer external artifact handling until content hardening.

    Screenshots, videos, generated outputs, and external demos are not public evidence yet.

Links

06

Relations

Relations

How public content model relates to the rest of the register.

Content dependencies

COLOPHON · № 04REC / public-content-model
Created
Updated
Record ID
REC / public-content-model
Version
0.1.0
State
candidate
Maintained by
azwerks
Derived from
Astro collection config, typed record helpers, public content report, and current content entries.

LimitsPublic data foundation; search indexing, feed metadata, and ongoing editorial workflow remain deferred.