Skip to content

For Teams — Migration Notice (v1.3.10)

Deprecated in v1.3.10

The docs/for-teams/ directory is deprecated in FCC v1.3.10 and will be removed in v1.5.0. Its pages remain in place so external links continue to resolve, but new readers should follow the pointers below.

Why the split

FCC v1.3.10 adopts a 9-audience canonical taxonomy that separates role-oriented concerns from team-scale concerns. The old for-teams bucket mixed workflow design (a developer concern), team scaling (an operator concern), shared governance (an architect or auditor concern), and adoption strategy (an architect concern).

Splitting the bucket makes it easier for a reader to find the single document they need without having to read five.

Where the content moved

The table below maps every page in the legacy directory to its new home.

Legacy page Primary destination Secondary destination
index.md For Operators For Architects
downstream-adoption-guide.md For Architects — Adoption For Operators — Rollout
team-workflow-templates.md For Operators — Workflow Playbooks For Architects — Workflow Patterns
multi-team-governance.md For Architects — Multi-Team Governance For Operators — Runbooks
team-scaling-guide.md For Operators — Scaling For Architects — Capacity Planning
shared-knowledge-base.md For Knowledge Engineers For Architects — Knowledge Infrastructure

Primary vs secondary destinations

The primary destination is the best fit for the full page. The secondary destination covers an orthogonal slice of the same content (e.g. the templates inside a workflow guide rather than the policies).

What happens to the old pages

Each legacy page now carries a deprecation banner at the top explaining the migration. The pages themselves have not been edited or truncated — they remain a faithful v1.3.9 snapshot so that external links and search-engine results still land on working content.

The pages will be frozen (no further edits) through v1.4.x and will be removed in v1.5.0 along with this migration guide.

For external linkers

If you maintain external references to pages in this directory:

  1. Update your links to point to the new audience section before v1.5.0.
  2. Use the Audience Cross-Links matrix to confirm the destination.
  3. For team-oriented content that doesn't cleanly map to one new audience, prefer for-operators — it is the closest cultural successor to the team perspective.

For contributors

New content must not be added to for-teams/. The nine-audience taxonomy is deliberately flat — if your topic fits across two or three audiences, use the cross-links matrix to pick the most-read audience for the canonical copy and cross-link from the others.

See also