Repository manualdocs/LOGGING_AND_TELEMETRY_GUIDE.md

Logging and Telemetry Guide

Canonical documentation rendered from the repository docs/ folder.

Logging and Telemetry Guide

This guide is the authoritative operational reference for Logging and Telemetry Guide in MD 2.0.3.

1. Daily TOML file model

Daily TOML file model is governed by explicit machine-readable policies and validated artifacts. Operators must preserve evidence, authority, compatibility, deterministic exit behavior, and honest limitations.

Required behavior

Resolve canonical sources before acting.
Record the selected contract and any exception.
Use least privilege and deterministic verification.
Emit telemetry without storing secrets.
Preserve cross-links, ownership, and review triggers.

Verification

[ ] Static structure is valid.
[ ] Runtime behavior matches the documented contract.
[ ] Failure behavior is explicit and fail-closed.
[ ] Cross-platform or cross-format parity is checked where applicable.
[ ] Residual unknowns are visible.

2. Event schema

Event schema is governed by explicit machine-readable policies and validated artifacts. Operators must preserve evidence, authority, compatibility, deterministic exit behavior, and honest limitations.

Required behavior

Resolve canonical sources before acting.
Record the selected contract and any exception.
Use least privilege and deterministic verification.
Emit telemetry without storing secrets.
Preserve cross-links, ownership, and review triggers.

Verification

[ ] Static structure is valid.
[ ] Runtime behavior matches the documented contract.
[ ] Failure behavior is explicit and fail-closed.
[ ] Cross-platform or cross-format parity is checked where applicable.
[ ] Residual unknowns are visible.

3. Append and rotation behavior

Append and rotation behavior is governed by explicit machine-readable policies and validated artifacts. Operators must preserve evidence, authority, compatibility, deterministic exit behavior, and honest limitations.

Required behavior

Resolve canonical sources before acting.
Record the selected contract and any exception.
Use least privilege and deterministic verification.
Emit telemetry without storing secrets.
Preserve cross-links, ownership, and review triggers.

Verification

[ ] Static structure is valid.
[ ] Runtime behavior matches the documented contract.
[ ] Failure behavior is explicit and fail-closed.
[ ] Cross-platform or cross-format parity is checked where applicable.
[ ] Residual unknowns are visible.

4. Prompt and scenario logging

Prompt and scenario logging is governed by explicit machine-readable policies and validated artifacts. Operators must preserve evidence, authority, compatibility, deterministic exit behavior, and honest limitations.

Required behavior

Resolve canonical sources before acting.
Record the selected contract and any exception.
Use least privilege and deterministic verification.
Emit telemetry without storing secrets.
Preserve cross-links, ownership, and review triggers.

Verification

[ ] Static structure is valid.
[ ] Runtime behavior matches the documented contract.
[ ] Failure behavior is explicit and fail-closed.
[ ] Cross-platform or cross-format parity is checked where applicable.
[ ] Residual unknowns are visible.

5. Review, consent, audit, and verification events

Review, consent, audit, and verification events is governed by explicit machine-readable policies and validated artifacts. Operators must preserve evidence, authority, compatibility, deterministic exit behavior, and honest limitations.

Required behavior

Resolve canonical sources before acting.
Record the selected contract and any exception.
Use least privilege and deterministic verification.
Emit telemetry without storing secrets.
Preserve cross-links, ownership, and review triggers.

Verification

[ ] Static structure is valid.
[ ] Runtime behavior matches the documented contract.
[ ] Failure behavior is explicit and fail-closed.
[ ] Cross-platform or cross-format parity is checked where applicable.
[ ] Residual unknowns are visible.

6. Metrics and durations

Metrics and durations is governed by explicit machine-readable policies and validated artifacts. Operators must preserve evidence, authority, compatibility, deterministic exit behavior, and honest limitations.

Required behavior

Resolve canonical sources before acting.
Record the selected contract and any exception.
Use least privilege and deterministic verification.
Emit telemetry without storing secrets.
Preserve cross-links, ownership, and review triggers.

Verification

[ ] Static structure is valid.
[ ] Runtime behavior matches the documented contract.
[ ] Failure behavior is explicit and fail-closed.
[ ] Cross-platform or cross-format parity is checked where applicable.
[ ] Residual unknowns are visible.

7. Privacy and redaction

Privacy and redaction is governed by explicit machine-readable policies and validated artifacts. Operators must preserve evidence, authority, compatibility, deterministic exit behavior, and honest limitations.

Required behavior

Resolve canonical sources before acting.
Record the selected contract and any exception.
Use least privilege and deterministic verification.
Emit telemetry without storing secrets.
Preserve cross-links, ownership, and review triggers.

Verification

[ ] Static structure is valid.
[ ] Runtime behavior matches the documented contract.
[ ] Failure behavior is explicit and fail-closed.
[ ] Cross-platform or cross-format parity is checked where applicable.
[ ] Residual unknowns are visible.

8. Querying logs

Querying logs is governed by explicit machine-readable policies and validated artifacts. Operators must preserve evidence, authority, compatibility, deterministic exit behavior, and honest limitations.

Required behavior

Resolve canonical sources before acting.
Record the selected contract and any exception.
Use least privilege and deterministic verification.
Emit telemetry without storing secrets.
Preserve cross-links, ownership, and review triggers.

Verification

[ ] Static structure is valid.
[ ] Runtime behavior matches the documented contract.
[ ] Failure behavior is explicit and fail-closed.
[ ] Cross-platform or cross-format parity is checked where applicable.
[ ] Residual unknowns are visible.

9. Failure recovery

Failure recovery is governed by explicit machine-readable policies and validated artifacts. Operators must preserve evidence, authority, compatibility, deterministic exit behavior, and honest limitations.

Required behavior

Resolve canonical sources before acting.
Record the selected contract and any exception.
Use least privilege and deterministic verification.
Emit telemetry without storing secrets.
Preserve cross-links, ownership, and review triggers.

Verification

[ ] Static structure is valid.
[ ] Runtime behavior matches the documented contract.
[ ] Failure behavior is explicit and fail-closed.
[ ] Cross-platform or cross-format parity is checked where applicable.
[ ] Residual unknowns are visible.

10. Retention and archival

Retention and archival is governed by explicit machine-readable policies and validated artifacts. Operators must preserve evidence, authority, compatibility, deterministic exit behavior, and honest limitations.

Required behavior

Resolve canonical sources before acting.
Record the selected contract and any exception.
Use least privilege and deterministic verification.
Emit telemetry without storing secrets.
Preserve cross-links, ownership, and review triggers.

Verification

[ ] Static structure is valid.
[ ] Runtime behavior matches the documented contract.
[ ] Failure behavior is explicit and fail-closed.
[ ] Cross-platform or cross-format parity is checked where applicable.
[ ] Residual unknowns are visible.