Agentic system runtime report

Type: types/type-spec.md

The runtime baseline: source-grounded invocations and alternate/forcing routes, and records under RT- IDs. It is written before the two specialist members and remains unchanged afterward. The source contract governs evidence; the record contract governs identity, fields, statuses and theory assessments.

Frontmatter

Field	Required	Use
type	Yes	agentic-systems/types/agentic-system-runtime-report.md
description	Yes	Retrieval description naming the system and the runtime boundary traced
run-id	Yes	The set's run ID
reviewed-boundary	Yes	The set's frozen revision or capture identity

Required sections

Runtime account

## Runtime account traces the ordinary shipped invocation and every material alternate or forcing route the runtime analyst selects. For each material loop it identifies the trigger and principal, identities, next-step owner, decision policy and representational form, context, state, executor and effect boundary, runtime-client controls, persistence, coordination and return, recovery, and terminal output. A load-bearing guarantee also names its owner, enforcement point, guarantee strength, covered and alternate paths, required external contract, and separate conclusion-status fields.

The account links to the route records for decision roles, answer oracles, operating modes and admission mechanisms, and to component records for model mutability. Those fields follow the shared record contract.

The account distinguishes inspected implementation from supplied execution evidence. Without supplied traces or experimental results, operation, activation and benefit remain unobserved. Missing execution evidence does not establish absent behavior.

Shared records

## Shared records contains this member's declarations under all six kind headings in the template. An empty kind says none declared in this member. Every record follows the shared record contract, including its conditional admission and theory fields.

Annotations

## Annotations holds only runtime-specific fields on records declared elsewhere, as #### On MEM-RTE-10 — Short label: admission and theory fields, decision roles, operating mode, answer oracle and links to runtime-declared records. It repeats no generic identity, evidence passage or memory finding. Ordinarily this section says none: the runtime is written before the other analysts declare records. Reconciliation attaches any later-needed runtime fields and amends this member's findings.

Template

---
type: agentic-systems/types/agentic-system-runtime-report.md
description: "Runtime baseline of {system} at {boundary}"
run-id: AAS-YYYY-MM-DD-system-slug-nn
reviewed-boundary: "{immutable revision or capture identity}"
---

# {System} runtime report

## Runtime account

## Shared records

### Components

### Operative objects

### Routes

### Claims

### Evidenced absences

### Behavioral-authority paths

## Annotations