Skip to content
Browse documentation
Controlled alphaValidatedClaude Code / Cursor · In development

Argos developer documentation

Engineering Lead Quickstart

Set one owner-approved project rule, confirm a new Task inherits it, and trace any exception through decision, execution, verification, and Evidence.

Before you start

1. Choose the project

  1. Sign in and choose the project from the project switcher.
  2. Open Team rules from the application navigation.
  3. Confirm the project name before making a rule. Rules never grant access to another project.

2. Approve one Team rule

An organization owner chooses a repository-relative path pattern, then selects REQUIRE APPROVAL or BLOCK and records the reason.

REQUIRE APPROVAL
Pause a matching supported mutation until an authorized reviewer decides the exact action.
BLOCK
Deny a matching supported mutation before execution.

The stored version records its rule key, owner approval, timestamp, path, effect, and reason. Members can read rules but cannot create, replace, disable, or weaken them.

3. Confirm a new Task inherits it

Start a new controlled Codex Task using the Developer Quickstart. Open the Task and find Team rules frozen for this Task. The frozen version is the effective rule snapshot for that Task; later rule changes do not rewrite it.

4. Decide a held exception

  1. Open Needs approval.
  2. Read the exact target, matching rule version, owner reason, and requested action.
  3. Approve or block only that held action. Approval authorizes continuation; it does not prove execution or correctness.

5. Follow the recorded outcome

Return to the Task, then open its Evidence. Read the decision, actual execution outcome, independent verification result, and rule provenance separately. A blocked action must remain not executed. An approved action can still fail verification.