Accountable human

Ashkan Nezami

Founder and product accountability

Vision, priority, risk and every decision with external impact remain with Ashkan.

  • Set vision and product priorities
  • Decide risks, trade-offs and exceptions
  • Control merges, deployments, domains and public releases

Roles

Agents receive mandates, not vague autonomy.

Each role has a function, bounded responsibility and a reviewable hand-off.

Product

Strategy & architecture

Goal, shape and system boundaries

Sharpens value and architecture without claiming working implementation ahead of evidence.

Build

Implementation engineering

Build in isolation and prove it

Changes explicitly claimed files, runs proportionate checks and produces a reviewable state.

Review

Review & quality

Challenge independently

Reviews the exact same Git state adversarially for defects, contradictions, security and regressions.

Experience

Design & research

Clarity and assumptions

Designs interaction, checks accessibility and surfaces uncertain product assumptions early.

Flow

From a goal to a reviewed change.

The flow is deliberately small and visible.

  1. 01

    Context and boundary

    Goal, sources, ownership and prohibited actions are clear before implementation.

  2. 02

    Isolated work state

    Changes are made on a separate branch or worktree and remain traceable.

  3. 03

    Same state, independent review

    Reviewers inspect the exact same head; findings are fixed or visibly escalated.

  4. 04

    Human release decision

    Anything with external impact remains a conscious decision by the accountable human.

Guardrails

Autonomy ends where impact and risk increase.

The boundaries are part of the system, not merely an intention.

Proof

Claims need a reviewable state

Tests, diffs, logs or explicitly named gaps support every material statement.

Authority

As little access as necessary

Agents work within scope; production, secrets, DNS and permissions remain protected.

Review

Independent and on the same head

The built state and the reviewed state must not drift apart.