# Matrix Documentation System Status

## Summary

Objective: create a linked documentation system for ZoneGaze Matrix that treats Matrix as the host
product and documents Flow as one plugin among the combined plugin set.

## Current Approach

- Replace Flow-first top-level indexes with Matrix-first indexes.
- Keep existing detailed Flow plugin docs, but move them under a Matrix-level navigation spine.
- Add missing codebase/package boundary READMEs where owner surfaces were under-documented.
- Add reference pages for APIs/contracts, tools/integrations, and repo-level upstreams.
- Add detailed plugin pages for every current Matrix plugin, including Research.
- Add explicit docs for skills/rules, hooks, and a Matrix-wide feature catalog.
- Add a plugin coordination guide plus per-plugin coordination sections so current versus planned
  Matrix plugin interplay is documented without overstating future behavior.
- Add business-facing documentation for marketing positioning, sales motion, and commercial guardrails
  so outward-facing narrative stays aligned with the actual product state.

## Verification

- `node scripts/check-docs.mjs` passed for 1126 Markdown files on 2026-07-08.
- New docs tree and package-boundary READMEs were reviewed for Matrix-first product framing.
- `node scripts/check-docs.mjs` passed for 1127 Markdown files after the plugin coordination slice
  on 2026-07-08.
- Current source review of `flow/contracts/src/zonegaze-products.ts`, `flow/common/src/plugin-services.ts`,
  and `extensions/social-studio/README.md` confirmed that Social Studio is part of the product
  catalog and should be included in both technical and business-facing documentation.

## Open Blockers

- None currently.

## Next

- Review any future plugin additions against `docs/extensions/plugin-coordination.md` so the
  current-vs-planned split stays accurate.
- Review any future pricing, donation, pilot, or packaging changes against
  `docs/business/commercial-posture.md` before marketing or sales copy is updated.
