← Documentation home

Canonical Markdown source · Oct 20, 2018

Product Surface Ownership

ops/product-surface-ownership.md · 31 lines · SHA-256 ba169a042067

Meta Museum deliberately keeps a broad expert workspace, but breadth must not

become anonymous maintenance cost. The operations-risk report assigns every

`app/**/page.tsx` route to one of seven review lanes and fails when a page has no

owner.

| Lane | Owner | Scope | Consolidation rule |

|---|---|---|---|

| Public trust | Trust | Home, Explore entry points, Stories, Connections, My Collection, daily/surprise discovery, professional-workspace entry, evidence, sources, docs, research-kit commerce, pilot, projects, and policy pages | Extend an existing public journey unless a new audience needs a distinct outcome. |

| Collection research | Curator Experience | Explore, records, entity, graph, IIIF, Linked Art, research reports/feeds, and mapping tools | Prefer tabs or progressive disclosure over another peer route. |

| Agent operations | AI Reliability | Agents, AI evaluations, automation, private research-approval review, and device-local validation preflight | Share task, approval, and evaluation contracts; do not create agent-specific copies. |

| Tenant operations | Tenant Safety | Organizations and organization scope | Keep identity, membership, and active-org state in one bounded lane. |

| Platform operations | Operations | Readiness, workers, issues, and roadmap | Prefer the readiness dashboard as the summary surface and link to specialist detail. |

| Curation | Curator Experience | Annotation and reconciliation queues | Preserve distinct review semantics while sharing queue primitives. |

| Authentication | Security | Product sign-in and callback handling | Keep one product-specific sign-in context and reject external callback URLs. |

Change gate

Before adding a page:

  1. Name its lane and owner in `PAGE_OWNERSHIP_LANES`.
  1. State the user outcome that cannot fit an existing route.
  1. Add route-level behavior and accessibility coverage.
  1. Run `pnpm exec tsx --test tests/services/operations-risk-controls.test.ts`.

API breadth remains governed separately by route-family ownership, auth,

organization-scope, and storage-write guards. High-churn scripts remain governed

by the evidence-script ownership registry and its preferred-entry-point and

pruning rules.