content-model: events - Reconcile profiles, editions and appearances #377

Outcome

Document the event/edition contract and approved historical/public-appearance boundaries.

Verified context

content/events/ provides flat profile metadata; data/types/events.ts includes editions, attendance, travel and relationships. Active and legacy events pages serve different purposes.

Scope

Produce field and inclusion decisions before implementing E2/E3.

Acceptance criteria

• Matrix covers identity, name/title, event classification, location, recurrence, editions, dates/status/role and narrative.
• Future confirmation, timezone, online location and links have applicability/approval decisions without invented values.
• Optional media, travel, taxonomy, FAQs and related content reuse existing contracts.
• Route/inclusion decisions distinguish historical profiles, confirmed appearances and placeholders; editorial verification stays separate.

Boundaries and sources

Creation defines work only; it does not start implementation. Preserve unrelated code, protected assets, editorial wording and existing records. Do not fabricate content, identity, media, manuscript chapters, dates or engagement data. Use approved repository-native authoring, validation, preview and publication decisions; do not provision an external CMS or database. Existing editorial verification remains with its current issues. All acceptance criteria remain unchecked until evidenced.

Repository evidence was inspected on develop at 4ecdb26d9655a48bf000a7c89da2f70383edce87. Recheck before implementation; no build or browser tests were run for this draft. Follow repository instructions and applicable Spec Kit requirements. Paths below refer to this repository.

Sources: repository instructions, application, editorial content.

Branch instructions

• Repository: lightspeedwp/ThisOneTimeOnAcidCom
• Proposed branch: docs/events-model-contract
• Base: develop
• Naming policy: local guide, validator, organisation strategy.
• Pull request template: Unresolved for this prefix in the inspected routing evidence; verify the current repository/organisation template before opening a PR.
• Constraints: Preserve unrelated changes; do not force-push, merge or deploy. Complete applicable Spec Kit requirements before implementation.
• Conflicts or missing evidence: Proposed branch, not an existing branch; collision freedom is unverified. Recheck current branch routing and open governance changes, including PR automation: repo-governance - Add governance automation and validation #346. Older instructions claim branch rules are absent; the inspected local guide and executable validator establish the current convention. This draft creates no branch or pull request.

Branch instructions — batch 29 audit addendum

• Repository: lightspeedwp/ThisOneTimeOnAcidCom; implementing target: this event-model reconciliation issue, counterpart GitHub issue 377 in this repository only.
• Proposed branch: docs/events-model-contract; base: refreshed develop, checked at 4ecdb26d9655a48bf000a7c89da2f70383edce87 (R). Organisation baseline: 8f28eca80bff198879f7aaf496717dc0551bb32e (O).
• Branch state: proposed new branch, not created/reused. Absent from returned complete branch listing; exact-head PR search found none. Recheck before creation; no automatic reuse of unrelated/governance work.
• Naming: repository local guide and validator authorise docs/type-scope-title for this documentation-only outcome. Static inspection, not executed validation. Preserve existing guidance; record conflicts with older no-conventions statements without rewriting them here.
• Template: canonical routing contract maps docs to documentation template. Routing advice is not native inheritance/body insertion. Verify selection before PR creation; no local copies, locked-template edits or automatic frontmatter metadata.
• Parent context: preserve hierarchy; omit coordination-parent identifiers/URLs from branches, PR metadata and coding prompts while association effects remain unverified. Never use parent as native development/closing target.
• Allowed closing targets: none currently. Partial reconciliation cannot close the issue; future references/associations require separate review. No linking syntax authorised here.
• Governance PR346 is unmerged context, not delivered infrastructure or reuse branch. No repository edits, branch/PR operations, execution, merge or deployment authorised.

Expected file changes

Proposed documentation-only contribution, not implementation authority. New paths absent from inspected parent directories at R; existing tracker verified. Exact specification reuse/allocation remains unresolved: preview any required specification/research/plan/tasks/catalogue edits separately. No number or specification path allocated here.

No moves/deletions. Creation-sample documentation claims four integrated events, but inspected mock aggregation exports only Origin. Historical profiles and upcoming attendance do not prove confirmed public appearances. Active events view currently contains placeholders/no public dates. Preserve discrepancies and unknowns; do not invent dates, attendance, bookings or media.

Prior loading/view plans are not delivered contracts. This contribution reconciles decisions, not runtime integration. Specification reuse versus new allocation and ownership remain gates; missing linked maintenance guidance remains a gap, not permission to invent policy.

Exclude application code, routes, types, loaders, editorial changes, assets/references, protected fallback component, Supabase, attribution/changelog, dependencies, managed workflows and deployment. Resolve changelog handling separately. No commands, scripts, installs, hooks, tests, builds or cloud operations performed. Extra paths/material changes require revised preview and approval. Exclude credentials/restricted content from public sync. Description approval changes no status, ownership, labels, hierarchy or PR associations and grants no implementation authority.