Post · phase 10
Phase 10 of 10

Archive

Store assets, close out, and decommission resources.

Family PostToken #475068Duration Moment
A

The intent

Why this phase exists

Keep the estate alive and governed for the long term. Discoverable, permissioned, rights-checked, and searchable, for as long as the client needs it.

Exit gate

Retention policy confirmed, permissions and rights expiry checked, access audited, and the archive is discoverable and searchable in WDS.

B

The agent → human handoff

Every agent task runs the same governed loop. The agent is triggered, it drafts, a named human reviews, and only then does it publish. Same shape in every phase.

The governed loop
D

The work, by actor

Our people

Craft & judgement

Craft, judgement and client-facing approval.
  • Event Manager — Confirm retention policy, permissions and ongoing access expectations are met.
  • Marketeer — Maintain discoverability, update links, reuse assets where relevant.
  • Producer — Keep programme metadata accurate, ensure speaker rights, enable reuse.
  • Technical Support — Keep the event searchable in WDS, enforce permissions, audit access.
Our agents

Scale & speed

AI drafts; a named human owns and approves.
  • Marketeer — Run SEO hygiene on archived pages.ownerMarketeer · trigger: scheduled
Our platform

Reliability

Deterministic WDS behaviour, no actor required.
  • Technical Production — Ensure long-term playback quality, storage integrity and monitoring exceptions handled.
C

What the client gets

Delivered

A permanent, governed content estate. Findable, watchable, rights-clean, for as long as it needs to live.

D

The safeguard

What could go wrong

Content stays public after the rights to it have expired.

Why it won't

Rights expiry checks and access audits are part of Archive, and the retention policy is confirmed, not assumed.

E

The thread continues

Wavecast Phase Playbook · internal conceptual reference
Phase tokens bound to the Colour Registry · wheel engine v1.3 · multi-actor delivery model.