Content operations

Daily operator loop

1. Check failed or waiting task runs and unresolved human reviews.
2. Triage community Link candidates; promote through the Tool editor or dismiss with a reason.
3. Review new Link evidence, current availability, canonical URL, and semantic fields.
4. Review Dimension membership, parent or edge context, resource counts, and introduction copy.
5. Publish content only after its sanitized body and source references are complete.
6. Inspect change records, daily matchup candidates, Push delivery failures, orders, and dead letters. Replay only after identifying a transient cause; otherwise resolve the exception with an investigation note.

Links and Tools

Link is the publication boundary. A Tool editor updates the Link and Tool extension atomically. Any editorial edit invalidates prior Link approval and returns it to draft. Publishing requires a canonical URL, complete copy, evidence, an AVAILABLE verification, and a current verification timestamp.

Repeated network failures move availability to an unreachable state; they do not prove the product is discontinued. Deprecation requires stronger page or human evidence.

Dimensions

Dimensions cover occupations, tasks, workflows, categories, audiences, and topics. Canonical parent links cannot form a cycle. Cross-type context belongs in DimensionEdge, while recommended Links belong in DimensionLink; both relations are constrained to one Site.

An empty Dimension cannot publish. It needs at least one child, edge, or Link relation plus reviewable introduction copy.

Content

Blogs, pages, and digests are stored as ContentItem. HTML is sanitized before persistence; scripts, event handlers, unsafe URL schemes, frames, and unsupported elements are removed. Model-generated items stay draft until output review succeeds.

Datasources and provenance

Every datasource declares rights and deletion behavior. Task outputs record source digests, observed time, package and policy versions, and provenance references. A model's prose is not evidence by itself.

Retirement and retention

Operators archive instead of physically deleting public facts. Public vote identifiers are removed after 90 days while aggregate counts remain. Push subscriptions retain encrypted endpoint material only until revocation or terminal provider expiry. Refunds revoke entitlements and download grants through the outbox worker.

Every business write and its action-ledger entry share one transaction; a ledger failure therefore fails the business write.