Operations explainer

Project-System Improvement

Project-system improvement starts from observed diff state, registered signals, source-bridged sidecars, or repeated workflow problems. It routes one bounded repair without smuggling physics continuation or broad system rewrites.

Read the loop Back to operations

Visual orientation only: improvement routing controls project machinery, not scientific claim status.

Improvement comprehension

Project-system repair is maintenance, not physics continuation.

The improvement route starts from observed diff state, registered signals, sidecar input, or repeated workflow problems, then classifies, resolves, executes one bounded packet, receipts, and closes, defers, or rejects explicitly.

Diagram showing observed diff or registered signal, classifier, advisory resolver, source-bridged sidecar input, one project-system AgentJob, documentation-impact and PASS evidence, close defer or reject signal, and no hidden physics continuation or signal closure by prose. — Static comprehension diagram: project-system improvement repairs research machinery through one bounded packet and explicit evidence.Mermaid source: docs/content-dossiers/operations-project-system-improvement/diagrams/project-system-improvement-loop.mmd. Manifest id: comprehension_operations_project_system_improvement_loop.

The diagram is a static reader aid. It does not replace the source files, route dossiers, or claim-status records that govern the topic.

Mechanism

How to read this surface.

Observe live state

Start from a diff, registered signal, repeated failure, source-bridged sidecar, or documented project-system problem.

Classify and resolve

The classifier names impact and reason codes; the resolver ranks current diff state, open signals, and sidecar context as advisory routing evidence.

Execute one packet

The selected repair runs as one bounded project-system AgentJob with write-path and claim boundaries.

Close with evidence

Signals close only with matching PASS completion evidence or a documented rejection decision.

Terms

Define the loaded words before using them.

Signal: A tracked project-system problem or improvement indicator.Not closed without matching evidence.
Sidecar: A project-improvement support artifact generated from qualifying source-bridge evidence.Input to routing, not replacement research handoff.
Resolver: A mechanism for ranking or choosing the next project-system packet.Advisory unless validators or concrete authority violations fail.
Documentation impact: Receipt for source and generated-surface impact in state-changing project-system work.Operational evidence, not physics status.

Boundaries

What this page must not imply.

No hidden physics work: Improvement packets stay project-system scopedA maintenance job cannot silently continue a physics derivation.
No signal closure by assertion: Receipts are requiredSignals need matching PASS evidence or a documented rejection/defer decision.
No global sidecar allowlist: Sidecar acceptance is exact-path scopedConditional sidecar acceptance applies only to the YAML/Markdown pair named by source-bridge metadata.

Safe reading

A useful summary also names the unsafe one.

Safe summary: Supported readingProject-system improvement classifies a live problem, routes one bounded project-system packet, records documentation-impact and PASS evidence, and closes, defers, or rejects signals explicitly.
Unsafe summary: Forbidden shortcutA project-system repair silently changes physics route, closes signals without evidence, replaces handoffs, globally allowlists sidecars, or expands role authority.

Related routes

Source basis

Use these as provenance, not primary navigation.

Source basis