AGPL-3.0-or-later · forever.

product · intent as code

Repeated AI work, written as a checked plan.

Nika turns work you repeat in chats and scripts into a file your team can read, check, run and verify.

The Nika workflow fieldA deterministic field connects intent, checking, execution and proof through one bounded path.
  1. 01Intent
  2. 02Check
  3. 03Run
  4. 04Proof
  1. 01

    Intent

    Write the repeated work as one readable file.

  2. 02

    Check

    Inspect the graph, permissions, requirements and known cost before execution.

  3. 03

    Run

    Execute locally with the model and tools the file names.

  4. 04

    Proof

    Keep a verifiable record of what ran and what it produced.

the product

Controlled workflow anatomy

A workflow is useful when you can understand and control it.

Nika turns intent, operating boundaries and run evidence into one inspectable object.
One plan you can readTasks, inputs and dependencies form one bounded system.
01 · intent fieldOne plan you can read

Tasks, inputs and dependencies form one bounded system.

Limits in the fileFiles, tools, network destinations and secrets are declared before work.
02 · boundary pathLimits in the file

Files, tools, network destinations and secrets are declared before work.

A record you can inspectOutputs, decisions, costs and changes accumulate as verifiable evidence.
03 · proof shellA record you can inspect

Outputs, decisions, costs and changes accumulate as verifiable evidence.

Boundary · before execution

The workflow declares its reach.

Nika checks the files, tools, network destinations and secrets named by the workflow before work begins.

See the boundary
01Files
Read inputs. Write named outputs.
02Tools
Allow only the operations the plan needs.
03Network
Name the destinations that may be reached.
04Secrets
Reference credentials without placing them in the file.
record · meeting-actionsexit 0
  1. 01invoke

    read the transcript

    observed
  2. 02infer

    extract action items

    observed
  3. 03agent

    verify owners and dates

    observed
  4. 04invoke

    write the named artifact

    observed
artifactaction-items.jsonboundary unchanged

Proof · after execution

The result keeps its history.

Inspect what ran, which decisions were recorded, what changed and which artifact the workflow produced.

Inspect a run record

Bring your own process

Start alone, or map the first workflow with SuperNovae.