Skip to content

Productsastack

Product index

Outcome first. Proof built in.

astack gives Codex one entry point for engineering work. Describe the outcome. It chooses a route, follows the relevant guidance, checks what happened, and brings kept code to a pull request.

Inspired by Poteto’s pstack, opens in a new tab

Explore astack, opens in a new tabView source on GitHub, opens in a new tabOPEN SOURCE · IN DEVELOPMENT
astack / Engineering routes

$applification:astack <task>

Choose a route by the intended outcome.

  • Feature

    Add or change user behaviour.

  • Bug fix

    Reproduce a defect and verify the fix.

  • Refactor

    Change structure while preserving behaviour.

  • Performance

    Measure slowness, then compare the result.

  • Investigation

    Answer a question from evidence.

  • Pull request

    Review or finish an existing change.

  • App control

    Make a running app controllable for verification.

Proof → Review → Pull request

A read-only investigation ends with an answer.

astack / The route map

One task. The right line.

All routing examples, opens in a new tab

Choose a request to trace its route.

These examples come from astack's routing evals. Each shows the expected decision, with the selected line highlighted below.

Scroll sideways to follow every route.

$applification:astack <task>

Choose a route by the intended outcome.

  1. Feature

    1. Agree the outcome
    2. Implement in slices

  2. Bug fix

    1. Reproduce the symptom
    2. Fix and rerun the path

  3. Refactor

    1. Name the invariant
    2. Change in small steps

  4. Performance

    1. Measure a baseline
    2. Change one cause

  5. Investigation

    1. Gather evidence
    2. Answer or advise

    Ends with an answer

  6. Pull request

    1. Read the full diff
    2. Trace affected consumers

  7. App control

    1. Build or adopt a CLI
    2. Prove a user path

  8. Project setup

    1. Inspect the repository
    2. Record local proof routes

For kept repository changes

  1. Proof

    Observe the result

  2. Review

    Check intent and quality

  3. Pull request

    Attach evidence and gaps

A compact view of the workflow. Investigation ends with an answer. Project setup is a task-specific path alongside the seven work routes.

Give the model room to do the work.

A clear outcome, project guardrails and a verification loop let the model take on larger tasks. astack selects checks that can catch the relevant failure and records what was actually observed.

A substantial behaviour change keeps a short contract with observable acceptance cases. Existing projects keep their working stack and tools.

Your project owns its decisions.

The Applification plugin supplies the workflow. Your project supplies its commands, environments and product decisions. A project profile records the local proof routes; a project-owned control CLI and feature map help the agent drive a running product.

Proof names the revision, environment, action and observed result. A passing test or screenshot supports the behaviour it actually exercised. Gaps stay visible in review.

TRY IT IN CODEX IN DEVELOPMENT

Open source. In development.

astack is available as the Applification plugin for Codex under the MIT licence. The workflow is still in development. The website explains the routes and installation; the repository holds the current skill and guidance.

Get started, opens in a new tabRead the repository, opens in a new tab

KEEP EXPLORING

Choose another product.

View all products