AGENTS.md git:20261101.d240412A

Immutable. This exact content never changes and is served at /api/v1/blob/933eac8d266c255e.

<!-- hyperfide-owned: generated-spec v1 -->
<!-- GENERATED by hyperfide spec render from spec/ kvx — DO NOT EDIT. -->

# Hyperfide Workflow

This file is a generated pointer. The single workflow source is `spec/workflow.kvx`; edit it and run `hyperfide spec render`, never this file.
hyperfide spec render owns AGENTS.md and CLAUDE.md; hyperfide agentmd owns agent-context.md in the configured context directory (.hyperfide/context by default; legacy .codify is migrated with backups); hyperfide codemap owns CODEMAP.md.

## Active feature

`spec/hyperfide-source-control/spec.kvx` — read its `[meta]` status, `[req.*]` acceptance criteria, and the `[task.*]` list (status + wave + requires). Work one task at a time in wave order; update `status` in the kvx as you go.

## The loop (every session)

1. hyperfide brief — load repo state, the active task and prior decisions.
2. hyperfide spec next — take the lowest-wave eligible task.
3. hyperfide spec start <id> — claim it in an isolated task worktree or sandbox.
4. hyperfide survey <area> for the wide picture, then hyperfide context <area> for the code you need.
5. Implement only the claimed task. Never default what you were not given: raise an Ask (MCP ask_raise, or hyperfide ask raise), keep working on what does not depend on it, and read the answer with ask_status. Raise a secret when a credential or token is missing (it is answered with a secret-ref, never a value); a variable when a configuration value, path or endpoint is unknown; a permission before anything destructive, outside the task's touches, or a new dependency; a decision when more than one design fits, naming the option you recommend; a question when the spec or a criterion is ambiguous, with your reading as the recommendation. secret, variable and permission block; decision and question proceed on the recommendation and are flagged ([asks]).
6. hyperfide review against the task's criteria; hyperfide guard for grounding, contract and hygiene; hyperfide anchors --stale for docs your edits outdated.
7. Update the task status in the feature spec.kvx, then commit explicit paths with a message tagged [spec:<feature>/<id>]. Publication beyond the task branch follows [publication].
8. hyperfide spec done <id> — qualification reruns verify_cmd; done means proven.

## Where the rules are

Principles, hard rules and policies live only in `spec/workflow.kvx`: `[principle]`, `[hard_rules]`, `[status_values]`, `[human]`, `[asks]`, `[publication]`, `[memory]`. Read them there.