Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 44 additions & 0 deletions docs/concepts/manual-loop-is-not-runtime-transport-self-running.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
# Manual Loop Is Not Runtime, Transport, Or Self-Running Evidence

Manual approved-loop evidence is not runtime, transport, self-running,
production, compliance, certification, product-completion, loop-completion, or
formal-standardization evidence.

## What The Manual Loop Shows

The manual approved-loop example can show that a human-approved task packet led
to bounded documentation work, that the resulting report returned to a human
decision gate, and that retry, second-attempt, autonomous-continuation,
transport/runtime, durable-persistence, hosted-shell, and model/tool-call counts
remained `0`.

## What The Manual Loop Does Not Show

The manual approved-loop example does not show:

- runtime execution;
- transport dispatch;
- HTTP hooks;
- RabbitMQ;
- watcher or polling behavior;
- durable persistence;
- hosted shell execution for bounded action;
- model or tool calls for bounded action;
- retry;
- second attempt;
- autonomous continuation;
- production readiness;
- compliance readiness;
- certification readiness;
- product completion;
- loop completion;
- formal standardization.

Any future work in those areas requires separate human approval and separate
evidence.

## Related Files

- [No retry, no autonomous continuation](../examples/manual-approved-loop-v0/no-retry-no-autonomous-continuation.md)
- [Bounded action report](../examples/manual-approved-loop-v0/bounded-action-report.md)
- [Proof is evidence, not approval](./proof-is-evidence-not-approval.md)
29 changes: 29 additions & 0 deletions docs/concepts/proof-is-evidence-not-approval.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
# Proof Is Evidence, Not Approval

Proof is evidence, not approval.

Evidence can support a later human decision, but it does not itself authorize
broader scope, implementation, publication, runtime execution, transport
execution, or a new lane of work.

## Approval Boundary

- A proof artifact can show custody, integrity, or observed work.
- A report can describe what happened under approved scope.
- A readback can summarize evidence for a human reviewer.
- A human decision record approves consequential next steps.

## Non-Claims

Proof is not production readiness evidence, compliance evidence, certification
evidence, product-completion evidence, loop-completion evidence, or formal
standardization evidence.

Manual approved-loop evidence is not runtime evidence, transport evidence, or
self-running evidence.

## Related Files

- [Manual approved-loop evidence chain](../examples/manual-approved-loop-v0/evidence-chain.md)
- [Human decision gate](../examples/manual-approved-loop-v0/human-decision-gate.md)
- [Manual loop is not runtime/transport/self-running](./manual-loop-is-not-runtime-transport-self-running.md)
49 changes: 49 additions & 0 deletions docs/examples/manual-approved-loop-v0/bounded-action-report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
# Bounded Action Report

A bounded action report is evidence about what happened under approved scope. It
is not permission to continue, retry, publish, standardize, or execute a new
lane.

## Illustrative Report Sketch

The YAML below is illustrative documentation, not a schema-valid HACP artifact.
Do not copy it as a base record; use the published schemas for validated
artifacts.

```yaml
bounded_action_report:
report_id: bar_manual_loop_v0_example
source_task_packet: task_packet_manual_loop_v0_example
approved_scope:
- "Create documentation-only evidence examples."
- "Keep copy vendor-neutral and non-hype."
- "Preserve proof-is-evidence-not-approval wording."
completed_under_scope:
- "Recorded the manual approved-loop evidence chain."
- "Recorded count boundaries for retries, continuations, and runtime work."
- "Returned evidence to the human decision gate."
not_performed:
- runtime execution
- transport execution
- HTTP hooks
- RabbitMQ
- watcher or polling behavior
- durable persistence
- hosted shell execution
- model or tool calls
- retry
- second attempt
- autonomous continuation
requested_next_step: request_human_decision
```

## Boundary

The report can support later review. It cannot approve another action, broaden
authority, or prove production/compliance/certification readiness.

## Related Files

- [Human decision gate](./human-decision-gate.md)
- [No retry, no autonomous continuation](./no-retry-no-autonomous-continuation.md)
- [Manual loop is not runtime/transport/self-running](../../concepts/manual-loop-is-not-runtime-transport-self-running.md)
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
# Docs-Backed Product Readback

A docs-backed product readback summarizes where the chain started, what was
approved, what was materialized, what returned to the human, which counts stayed
zero, and what was explicitly not authorized.

## Readback

Readback id: `docs_backed_product_readback_manual_loop_v0`.

The manual approved-loop v0 chain started with a human-approved task packet. One
local manual attempt produced one bounded action report under the approved
scope. The report returned evidence to a human decision gate. A later follow-up
action, separately approved by a human, produced one later follow-up action
report and stopped again at a human decision gate.

The readback does not claim completion of the product, loop, runtime, transport,
self-running behavior, production readiness, compliance, certification, or
formal standardization.

## Preserved Counts

| Counter | Value |
| --- | ---: |
| First local manual attempt report count | 1 |
| Later follow-up action report count | 1 |
| Retry count | 0 |
| Second attempt count | 0 |
| Autonomous continuation count | 0 |
| Transport/runtime count | 0 |
| Durable persistence count | 0 |
| Hosted shell count for bounded action | 0 |
| Model/tool-call count for bounded action | 0 |

## Related Files

- [Evidence chain](./evidence-chain.md)
- [Human decision gate](./human-decision-gate.md)
- [No retry, no autonomous continuation](./no-retry-no-autonomous-continuation.md)
- [Proof is evidence, not approval](../../concepts/proof-is-evidence-not-approval.md)
42 changes: 42 additions & 0 deletions docs/examples/manual-approved-loop-v0/evidence-chain.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
# Manual Approved-Loop v0 Evidence Chain

This example shows a local, manual approved loop. It starts with a
human-approved task packet, records bounded action/report evidence produced
under that authority, and returns to a human decision gate before any next lane
is approved.

This is documentation evidence only. It is not runtime evidence, transport
evidence, self-running evidence, production evidence, compliance evidence,
certification evidence, product-completion evidence, loop-completion evidence,
or formal-standardization evidence.

## Chain

1. A human approves a bounded task packet.
2. A single local manual attempt produces one bounded action report.
3. The report records evidence about what happened under the approved scope.
4. The evidence returns to a human decision gate.
5. A later follow-up action, separately approved by a human, produces one
later follow-up action report.
6. The loop stops again at a human decision gate.

## Count Boundaries

| Counter | Value |
| --- | ---: |
| First local manual attempt report count | 1 |
| Later follow-up action report count | 1 |
| Retry count | 0 |
| Second attempt count | 0 |
| Autonomous continuation count | 0 |
| Transport/runtime count | 0 |
| Durable persistence count | 0 |
| Hosted shell count for bounded action | 0 |
| Model/tool-call count for bounded action | 0 |

## Related Files

- [Human decision gate](./human-decision-gate.md)
- [Bounded action report](./bounded-action-report.md)
- [No retry, no autonomous continuation](./no-retry-no-autonomous-continuation.md)
- [Proof is evidence, not approval](../../concepts/proof-is-evidence-not-approval.md)
54 changes: 54 additions & 0 deletions docs/examples/manual-approved-loop-v0/human-decision-gate.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,54 @@
# Human Decision Gate

A human decision gate records what is approved, what remains denied, what
evidence supports the decision, and which future work still requires a separate
approval.

Evidence can inform the decision. Evidence does not approve the next step by
itself.

## Illustrative Decision Gate Sketch

The YAML below is illustrative documentation, not a schema-valid HACP artifact.
Do not copy it as a base record; use the published schemas for validated
artifacts.

```yaml
decision_gate:
decision_id: hdg_manual_loop_v0_example
selected_decision: accept_follow_up
approved_next_step:
description: "Apply the approved documentation-only follow-up."
scope:
- "Use the reviewed evidence chain."
- "Edit only the approved documentation paths."
denied_authority:
- runtime execution
- transport dispatch
- retry
- second attempt
- autonomous continuation
- production readiness claim
- compliance claim
- certification claim
- formal standardization claim
evidence_refs:
- bar_manual_loop_v0_example
- docs_backed_product_readback_manual_loop_v0
Comment thread
joefeser marked this conversation as resolved.
requires_separate_future_approval:
- any runtime, transport, or self-running implementation
- any schema or protocol semantics change
- any production, compliance, certification, or standardization claim
```

## Boundary

A human decision record approves consequential next steps. A report, proof,
receipt, checksum, or readback does not.

## Related Files

- [Evidence chain](./evidence-chain.md)
- [Bounded action report](./bounded-action-report.md)
- [Docs-backed product readback](./docs-backed-product-readback.md)
- [Proof is evidence, not approval](../../concepts/proof-is-evidence-not-approval.md)
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# No Retry, No Autonomous Continuation

The manual loop preserves retry count `0`, second attempt count `0`, and
autonomous continuation count `0` unless a later human decision explicitly
approves different authority.

## Boundary Counters

The YAML below is illustrative documentation, not a schema-valid HACP artifact.
Do not copy it as a base record; use the published schemas for validated
artifacts.

```yaml
manual_loop_boundary:
retry_count: 0
second_attempt_count: 0
autonomous_continuation_count: 0
transport_runtime_count: 0
durable_persistence_count: 0
hosted_shell_count_for_bounded_action: 0
model_tool_call_count_for_bounded_action: 0
next_status: needs_human_decision
```

## Stop Rule

After the bounded action report is created, the loop stops. Continuing requires
a human decision record that names the next approved step and the denied
authority that remains denied.

This example does not introduce runtime, transport, HTTP hooks, RabbitMQ,
watcher/polling behavior, durable persistence, hosted shell execution,
model/tool calls, retry, a second attempt, or autonomous continuation.

## Related Files

- [Evidence chain](./evidence-chain.md)
- [Human decision gate](./human-decision-gate.md)
- [Manual loop is not runtime/transport/self-running](../../concepts/manual-loop-is-not-runtime-transport-self-running.md)