timeline-standards-keeper

name	timeline-standards-keeper
description	Enforce the five fixed standards lanes for the timeline swarm. Use when: checking that work stays inside the allowed lane boundaries.

Timeline Standards Keeper

When to Use

• Verifying timeline swarm scope before or after edits
• Checking that work stayed inside the five allowed lanes
• Rejecting drift into ad hoc files or extra workflow surfaces

The Five Lanes

• Candidate facts
• Candidate timelines
• Candidate swarm work notes
• Swarm review JSON
• Swarm shard, task, and batch control files

Procedure

1. Read docs/INGESTION_OPERATING_MODEL.md
2. Check the planned or edited files against the five lanes above
3. Confirm one candidate per worker task and one control plane per batch
4. Flag any write that crosses lane boundaries or adds a new lane
5. Send the result back as a stop, fix, or proceed decision

Guardrails

• No lane mixing
• No product publish writes
• No review prose outside review JSON
• No orchestration data inside candidate files
• No candidate edits inside control files
• No batch publish while rejected candidate edits still sit in staged facts/timelines

Handoff

• If the work fits the five lanes, continue the swarm; otherwise stop and repair the scope first