# Telemetry / Operational Signal

- Name: Telemetry / Operational Signal
- Catalogue ID: WM-SFT-017
- Registry ID: vr.wm-sft-017
- Type: Published Vercy entity
- Version: 0.1.0
- Specification: https://ver.cy/models/wm-sft-017-telemetry-operational-signal/spec.yaml
- Storage type: format-independent; select a binding in the page constructor
- Interface: https://ver.cy/models/wm-sft-017-telemetry-operational-signal/#template-builder
- Processes: https://ver.cy/processes/
- Model agent protocol: https://ver.cy/model-agent-protocol.md
- Research evidence: https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-sft-017

Read this file first, then `spec.yaml`. Traverse Bundle to Layer to Finding to
Questions and Artifacts. The specification is published, while its research
assurance remains `reviewable-draft`. Do not claim canonical completeness
while `researchAdjudication.publicationHolds` is non-empty. Preserve source
references, master-system identity and access rules.

## Five-facet gate

Before creating or changing an instance, inspect the specification for explicit
coverage of: identity and class; direct properties; recognition and observation;
capabilities, behaviour and possible actions; context and evidence. Treat each
facet as required, optional, not applicable with a reason, or delegated through
a pinned model reference. Do not invent physical properties for abstract
objects. For physical measurements preserve units, tolerances, method,
conditions, observation time, uncertainty and provenance.

Keep capability, behaviour, state, transition, affordance, operation,
precondition, effect, reversibility, permission, constraint, hazard and failure
mode distinct. Resolve delegated child models and master systems instead of
copying their domains into this model.

## Agent lifecycle route

1. **Fill:** read the nearest owner and Dimension policies, resolve master
   identities, ask only for missing facts or authority, then record facts,
   hypotheses and unknowns distinctly with evidence and observation time.
2. **Extend:** propose a versioned extension when the published bundles and
   layers cannot express a required concept. Preserve stable IDs and namespace
   ownership; do not silently widen the model boundary.
3. **Edit:** validate authority, purpose, current version and concurrency before
   mutation. Preserve history and provenance. Treat access expansion, external
   writes and material side effects as confirmation-gated actions.
4. **Validate:** run schema, semantic, reference, permission, evidence and
   five-facet checks before and after a write. Report unresolved references,
   lossy projections, stale observations and publication holds.
5. **Retire:** deprecate and supersede through the declared lifecycle. Preserve
   immutable history and resolvable references. Require confirmation before
   deletion, destructive migration or irreversible external action.

Autonomous work is limited to policy-authorized reading, local population of
confirmed facts, validation, indexing and non-destructive maintenance. Propose
schema changes and new imports. Require confirmation for publication, broader
access, external writes, deletion and irreversible effects. Follow the model
agent protocol and the nearest local `AGENTS.md` whenever their rules are more
restrictive.

## Local research assurance

This package was generated locally only. Codex is the sole active provider.
Claude and Grok were skipped under the owner-authorized waiver with zero
attempts. The separate no-tools Codex self-audit is not independent review.
Publication lifecycle metadata does not establish remote availability.

- Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; this local Codex self-audit is not an independent second-provider review.
- Direct HTTP and immutable source-version verification remain pending. No direct requests were attempted because the owner reports sandbox blocking; zero HTTP 200 responses were measured. Selected browser text and retrieval limits are documented in source-review.md. The coordinator must run check_sources.py outside the sandbox and review versions, errata and applicability.
- Executable metric/log/span profile schemas, unknown-state vocabularies, protocol adapters, versioned neighbor bindings and adversarial instance fixtures remain incomplete. Structural research validation is not runtime or protocol conformance.
- Adopting-profile review must establish content classification, authorized purposes, lawful retention, residency, external disclosure controls and custodian authority before operational use; no universal legal or security compliance is claimed.
- Continuous profiling, whole-trace/stream aggregates, workload-specific sampling bias and quantitative error estimation remain deferred; coverage is limited to the registry's metrics, logs and traces purpose.
- Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft.