Back to corpus
architecturetechnical paper candidatescore 30
Pulse Protocol — Autonomous Loop Architecture
> Multi-iteration autonomous development sessions with signal control, context chaining, and evidence-tracked completion.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
> Multi-iteration autonomous development sessions with signal control, context chaining, and evidence-tracked completion.
**Statuses**: pending → running → complete | blocked | failed | aborted | paused
### Inferred Signals (fallback) If no explicit tag, the system infers from output patterns:
| Pattern | Inferred Signal | |---------|----------------| | "all tasks are complete", "implementation is complete" | COMPLETE | | "need your input", "please provide", "cannot proceed" | BLOCKED | | Code blocks present, "created file", "next step" | CONTINUE | | No recognizable pattern | BLOCKED (safe default) |
| Priority | Strategy | Source | |----------|----------|--------| | 1 | Chained | Previous iteration's `anchor_hint_next` | | 2 | Explicit | Session's `anchor_turn_id` (set at creation) | | 3 | Semantic | RAG++ query with session goal | | 4 | Temporal | Most recent turn in project |
Promotion decision
What has to happen next
Promote into a technical note or architecture paper with implementation anchors.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.