[Tiago0507]

What changes

Adds full-platform/status.md, the status document gitops spec 009 T158 names.
It records what is true now rather than what the specifications intend.

Its first table is the fact a reader needs before any other: every managed
cluster registration activates zero applications, zero infrastructure roots and
zero environments. Nothing is deployed anywhere. The rest covers the exact
trade-offs, the data-continuity limits, the traffic status, the rollback path,
and the read-only commands an operator runs.

Why

T158 requires a verified statement of current state, and there was none. The
rollout index describes the intended stage order, and the specifications
describe the target, but nothing said what is actually running. A reader who
saw the size of the desired state could reasonably assume most of it was live;
none of it is.

The document is written so that assumption cannot survive its first table.

Tasks

gitops specs/009-full-platform-rollout T158 (advanced, not ticked)

• The task register is updated in this pull request
• Every task ticked here was verified by locating its artifact

No task is ticked here, and the register is not updated here. T158 also names
three documents in microservice-app-gitops (docs/profiles.md,
clusters/README.md, docs/bootstrap-boundary.md). It is ticked in that
repository once those land, which is also where its register lives.

How it is verified

Every claim about desired state was read from a file, not recalled. The
activation table comes from the registrations themselves:

$ for c in eks-dev eks-full-dev eks-full-staging eks-full-prod local-kind; do
    for k in apps infrastructure environments; do ... done; done
eks-dev            apps 0   infrastructure 0   environments 0
eks-full-dev       apps 0   infrastructure 0   environments 0
eks-full-staging   apps 0   infrastructure 0   environments 0
eks-full-prod      apps 0   infrastructure 0   environments 0
local-kind         apps 0   infrastructure 5   environments 0

The reason for the economical zero is quoted from the file's own header, in
clusters/eks-dev/activation-infrastructure.yaml: dependency cleanup is
complete, so no infrastructure child Application remains active before a
Terraform teardown. The previous list is preserved in
activation-infrastructure-retired.yaml.

Every artifact the document names was located before it was named:

tests/policy/no-imperative-managed-mutations.bats   present
tests/contract/economical-public-entry.sh           present
docs/bootstrap-boundary.md                          present
docs/namespace-isolation.md                         present
scripts/managed/verify-namespace-isolation.sh       present
research.md Decision 10                             present

One claim was wrong and was corrected before publishing. A first draft
placed the log shipper at infrastructure/alloy. That root does not exist:
Alloy is alloy.yaml and alloy-config.yaml inside infrastructure/loki. The
table now says so.

Nothing live is asserted. This authoring environment holds no cluster
credentials, and the document says that in its header rather than implying
otherwise. It states that the collectors report BLOCKED today and that a
BLOCKED verdict is the correct result, not a failure to investigate.

• Infrastructure changes: the documentation consulted through the required MCP servers is listed above

This pull request adds one Markdown file to a documentation-only repository and
changes no infrastructure, no provider argument and no version. Its source was
the repositories themselves, read at main.

Risk and rollback

A new document in a repository with no executable code. It changes no behavior.

The risk worth naming is the document going stale: it is a point-in-time
statement, dated in its header, and its closing table lists the five events that
would change it. Rollback is git revert of the merge.

What this PR does not do

• No register update and no task ticked, for the reason given under Tasks.
• No change to the three GitOps documents T158 also names. Those follow in a
  GitOps pull request, which is also where T158 is ticked.
• No claim that anything runs. The document's purpose is the opposite.
• No change to rollout-index.md, which governs stage order and remains the
  authority on it.

Merge method: squash. There is no SDD pair here; this is a document.

Approval required: one approval from EstebanGZam or Juanmadiaz45. No AI
agent approves it.

🤖 Generated with Claude Code