Events, calendar, and artifact SoD (anchor)¶
Indexed at: README.md — Read order (step 14).
Owns: time/event stance and separation of duties for calendar vs machine state vs local tool output. Does not own: URL lists, product specs, or conference schedules.
Stance (generic; do not duplicate elsewhere)¶
- Session “today”: use operator /
user_infowhen the workspace provides it. - Any conference, summit, launch, or deadline (Drupal events, vendor days, internal milestones): treat as upcoming only if the operator has it in an authoritative roster (GitLab milestone/issue, Wiki, or
plans/_ACTIVE/<initiative>/with a named owner and dates). Otherwise do not assume prep urgency, travel, or registration state. - After an event passes: do not keep treating it as “current prep” relative to the session date unless the operator reopens follow-up work.
Separation of duties (concern → single owner)¶
| Concern | Canonical owner (one truth) | Do not duplicate into |
|---|---|---|
| Layered portfolio, P0–P4, Agent Blu | ai.json → portfolio_model and BLU-PORTFOLIO.md |
Parallel “flat backlog” tables in random plans/ |
| Narrative layer order (releases) | ai.json → engineering_focus |
Markdown that reorders layers ad hoc |
| URLs, gateways, blockers | STATUS.json |
This file; ad hoc agent session exports |
Domains, context_hub, machine catalog |
ai.json |
Plans prose that restates the same tables |
| Product / protocol architecture | plans/__FINAL-PLANS/{Product}/ (+ OpenAPI where applicable) |
Local IDE/Claude output trees (below) |
| Ownership / SoD prose | BLU-OWNERSHIP.md |
Random *.md in repo root |
Read order for .agents/context/ |
README.md |
Parallel “start here” files |
| GitLab / BuildKit / credentials | BLU-OPERATOR-CONTRACT.md |
Session scratch paths |
DRY rule: If a fact already lives in the owner cell, link to that file or JSON key — do not copy tables, URL inventories, or priority stacks into this anchor.
Local agent outputs (not canonical)¶
Pattern: ~/Library/Application Support/Claude/**/outputs (and similar IDE/agent session export dirs).
| Property | Rule |
|---|---|
| Versioning | Not part of the blueflyio git contract unless promoted via MR into plans/ or product repos. |
| SoD | Operator decides what gets promoted; agents treat outputs as scratch / deliverables-in-flight, not architecture of record. |
| Promotion | If something must become durable: move or summarize into plans/_ACTIVE/ or plans/__FINAL-PLANS/ (per BLU-WORKSPACE.md), then link once — no long-lived duplicate “master plan” in both places. |
Example (cleaned 2026-04-22): Session tree .../local_ditto_5a4a7cf6.../outputs duplicated the old plans/outputs/ recipe and SDC trees and older sprint Markdown. Unique JSX/LinkedIn artifacts were copied to plans/_ARCHIVE/2026-04-22-claude-local-ditto-outputs/; the Library outputs folder was emptied after promotion.
Example (retired 2026-04-21): Repo path plans/outputs/ was a build dump; authored pieces moved into plans/__FINAL-PLANS/ domains, the duplicate SDC manifest stayed superseded by plans/blueflyio/Plans/SDC_COMPONENTS_MANIFEST.md, and the rest froze under plans/_ARCHIVE/2026-04-21-plans-outputs-retired/. Only plans/outputs/README.md remains as a pointer (see that file).
Canonical handoffs (links only)¶
| Need | Open |
|---|---|
| Platform catalog | ai.json |
| Ledger / health | STATUS.json |
| Index | README.md |
| SoD / domains | BLU-OWNERSHIP.md |
| Drupal stack | BLU-DRUPALCMS.md |
| Layered portfolio (human one-pager) | BLU-PORTFOLIO.md |
External (community calendars)¶
Use the official site for each community (e.g. Drupal: https://www.drupal.org/event/). Do not mirror schedules here.