DOT features

This public index describes accepted or release-candidate product behavior. Private implementation plans and operational evidence remain in the separate devs-guide/prompts lifecycle workspace.

0.0.7

Feature	Status	Public owners
Required `#STORAGE` and `#FILES` persistence lifecycle	Candidate	`STORAGE-001` through `STORAGE-012`
Required `#PROGRESS` and evidence-based `#LAZY` recovery	Candidate	`PROGRESS-001` through `PROGRESS-008`
Verified 15-minute cron-style project health checks	Candidate	Agent configuration and Progress contract
Need-based shared `agent:<term>` locations or Projects	Candidate	Storage configuration, registry, and Template records
Immutable Research ZIP checkpoints and recovery manifests	Candidate	Storage, Project, and Template contracts
CSV/JSON machine pairs with complete Markdown views	Candidate	Data and Template contracts
Agent configuration schema v3	Candidate	Agent configuration and schema

0.0.6

Feature	Status	Public owners
Configured `#TABS` domain inside Browser	Accepted	Agent configuration and Browser contract
Shared tab inventory, leases, and project queue	Accepted	`TABS-001` through `TABS-004`
Scheduled-or-event-driven blocker monitoring	Accepted	`TABS-005`
Evidence-based recovery and material notifications	Accepted	`TABS-006` and `TABS-007`
Agent configuration schema v2	Accepted	Agent configuration and schema

0.0.5

Feature	Status	Public owners
Evidence-completing on-demand Summary	Accepted	Summary contract and Project controls
Required subject-by-fact coverage matrix	Accepted	Summary and Template contracts
Default bounded public-source gap filling	Accepted	Summary and Internet contracts
Immutable parent inputs and successor evidence/data versions	Accepted	Summary and Data contracts
Summary v2 request, matrix, and completion validation	Accepted	Template contract and GitHub Actions

0.0.4

Feature	Status	Public owners
Repository-wide release contract	Accepted	`docs/release.prompt`
Compact core plus conditional release modules	Accepted	Release contract and release validator
Sequential stacked-release publication	Accepted	Release workflow and GitHub Actions
Release contract rendered and raw routes	Accepted	Publication manifest and Pages validation
Immutable archive handoff for manual Agent testing	Accepted	Release record and DOT ingestion entrypoint

0.0.3

Feature	Status	Public owners
On-demand subtopic executive brief	Accepted	Summary contract and Project controls
Self-contained, Fact-bound PDF narrative	Accepted	Summary and controlled Research records
Executive Brief Request and Completion Receipt	Accepted	Template contract
Summary ingestion and Pages routes	Accepted	Ingestion and publication manifests
Summary contract and delivery validation	Accepted	GitHub Actions

0.0.2

Feature	Status	Public owners
Agent operating contract	Accepted	`dot/agent/`
Tagged-release ingestion and activation gate	Accepted	`dot/ingest.json`, Agent, Project, and Template
Project → Internet → Data → Template research flow	Accepted	`dot/research/`
Evidence-to-dataset release lifecycle	Accepted	Data contract, reusable structures, and GitHub validation
Ordered assigned models and project-opt-in VM tools	Accepted	Agent configuration and Project contract
Page, Fact, browser, CAPTCHA, video and transcription contracts	Accepted	Agent modules and Research contracts
Clause-level migration audit	Accepted	History ledger and GitHub Actions
Legacy route compatibility	Accepted	Publication manifest and Pages builder

0.0.1

Feature	Status	Public owners
Core DOT protocol	Accepted	`dot/prompts/core/`
Reusable research starters	Accepted	`dot/prompts/research/`
Dated agent operating guides	Accepted	`dot/agents/`
Tiered documentation site	Accepted	`actions/`, `www/`, and the publication manifest
Validated release workflow	Accepted	repository, Pages, and release validators

A feature becomes accepted only when its source, GitHub Actions build/test checks, live Pages routes, and applicable human review gates all pass on the same commit. Compilation, builds, and tests do not run locally.