# Stage 3D Production Evidence Request

Status: pending authorized operator evidence. This document is an external
handoff request; it does not authorize production access, create a grant or
Policy, permit a query, or approve a mutation.

## Purpose

Stage 3D requires a verified production inventory before a governed platform
Type-revision Operation can enter BUILD. The detailed evidence contract and
the known STAGING baseline remain in the
[Stage 3D semantic authority audit](data-defined-semantics-audit.md).
The [implementation status](status.md) records the current production gap.

The repository does not identify a production operator or an approved
production inspection route. The project owner or existing organizational
authority must designate both before collection. Collection must use an
existing approved read-only mechanism, or an approved operator-provided export;
this request is not that authorization.

## Current route audit

The repository audit found no approved production collection route. The
remote registration diagnostic is explicitly STAGING-only and its database
checks are partial. Release and activation tooling transports or switches
files, while the legacy database scripts have no production-specific
read-only authorization contract and some are mutation-capable. A target
connection setting is not production authorization. Do not repurpose any of
these mechanisms for production collection.

The smallest capability that must be approved or supplied is a production
host or database-operator export against a positively identified production
target, using a dedicated read-only account or equivalent read-only
snapshot/export boundary. The method must be able to produce the complete
package below without deployment, provisioning, reconciliation, grant or
Policy changes. This request does not create that capability or authorize
production access.

## Required non-secret evidence package

The designated operator must provide a reproducible package containing the
following, limited to the minimum values needed to verify identity,
revision, provenance, authority and dependencies:

### Collection context

- production environment identity, target/application identity and environment
  classification;
- collection timestamp, timezone and relevant release/build identifier;
- the exact repository tool, approved diagnostic, export or query procedure
  used;
- the authorization or change/reference identifier permitting the read-only
  collection; and
- verification that the package represents production, not STAGING, a
  disposable clone or an inferred source-file state.

### Platform Types and history

- all 21 platform Type Object IDs, including the complete expected identity
  set;
- each current Object version, Type revision, platform scope and complete
  persisted descriptor;
- each retained historical Type revision, including revision number,
  descriptor, `provenance_ref`, `command_id` and recorded timestamps where
  present;
- the Type-of-Type binding for every Type Object; and
- any missing, duplicate, invalid, incompatible or source-versus-persisted
  descriptor discrepancy, with the affected identity named explicitly.

### Dependent Objects and platform structure

- every dependent Object ID and its exact Type Object ID and Type revision
  reference;
- Project Objects and all retained Project revisions;
- Authority Grants and Policies, including target scope and the relevant
  platform authorization configuration;
- Commands and their linked Action Execution, Attempt, Outcome, Event and
  Provenance evidence where present;
- View Definitions and Presentation Objects;
- Workflow Definitions and Workflow Authority Bindings; and
- Definition publication evidence and the configured Definition publisher
  authority, without exposing credentials or other secrets.

### Provisioning and reconciliation

- the provisioning/reconciliation implementation identity and release version
  used by the production environment;
- evidence of whether provisioning can write or rewrite `objects.value_json`
  or `object_revisions.value_json` at revision 1;
- any observed revision-1 overwrite, drift, failure or reconciliation event;
  and
- any production/STAGING difference relevant to Type identity, revision,
  provenance, dependent references or authority.

The package must identify exceptions rather than silently omit them. The
existing STAGING snapshot is a comparison baseline only; it cannot substitute
for production evidence.

## Read-only collection requirements

Before collection, the designated authority must verify that the chosen route:

1. targets the positively identified production environment;
2. is authorized for read-only inspection or export;
3. cannot insert, update, delete, revise, reconcile, deploy, activate or
   change grants, Policies, credentials or configuration;
4. does not request or disclose passwords, tokens, private keys, connection
   strings or other secrets; and
5. can produce the complete inventory above, including exact revisions,
   provenance and dependent references.

If an existing mechanism cannot establish these properties, it must not be
used for this request. Do not create a new inspection endpoint, bypass the
application boundary, or query production from an unapproved local tool as
part of this handoff.

## Operator attestation

The designated operator must return this attestation with the package:

```text
operator / role: _________________________________________________
production environment identity: _________________________________
collection timestamp (with timezone): ____________________________
approved collection method and authorization reference:
___________________________________________________________________

I attest that the supplied package was collected from the identified
production environment using the stated authorized method, that the method
was read-only, and that no Object, revision, grant, Policy, credential,
configuration, deployment state or other runtime state was modified.

operator signature or attributable approval: ______________________
date: ______________________
```

Do not include passwords, tokens, private keys or other secrets in the
package or attestation.

## Evidence acceptance gate

The production evidence prerequisite passes only when:

- the environment and collection method are positively identified;
- all 21 Type Objects are accounted for, or every exception is explicitly
  resolved;
- current and historical revisions, provenance and dependent references are
  complete;
- Project, authority, Command, presentation, workflow and publication
  dependencies are accounted for;
- provisioning/reconciliation behavior and any revision-1 overwrite risk are
  documented;
- production/STAGING differences are reconciled or explicitly explained; and
- the read-only attestation is attributable to the authorized operator.

Incomplete, contradictory, inaccessible, inferred or non-reproducible
evidence keeps the gate **NO-GO**. The package must be reviewed against the
owner decision and the canonical Stage 3D contract before any BUILD decision.

## Outstanding human action

An authorized organizational authority must first designate the operator and
approve the collection route. The designated operator must then collect and
return the package above. No identity or contact detail is established by the
repository, and this document does not designate one.