{ }Dwi

Dwi by thienhoc

Bound the work. Show the proof. Keep the decision human.

Dwi makes one piece of work legible: the allowed boundary, the packet of facts, the observed proof, and the moment a person decides what happens next.

Human Decision Funnel

A human sets the boundary, a packet carries the relevant facts, observed proof is checked, and the decision remains with the human.

Swipe the diagram to follow the route.

{ }Human intentname the job{ }Work boundaryallowed touchCase packetfacts togetherObserved proofcheck first{ }Human decisionapprove · correct ·exitDashed graphite route:proposed or retry
  • Orange-red { }: human boundary, contract, or gate
  • Light-gray •: packet or checkpoint
  • Solid graphite route: observed or approved
  • Dashed graphite route: proposed or retry
Orange-red braces denote the human boundary, contract, or gate. The light-gray bullet denotes a packet or checkpoint.Read it from left to right: choose the work, check the result, then make your own choice.
Text equivalent
  1. A person names the work boundary.
  2. One packet gathers only the facts needed for this case.
  3. Observed proof is reviewed before the next step.
  4. A person chooses to approve, correct, or exit.

One case, made readable

Choose the work. Check what happened. Decide the next step.

The same material is paced as a short editorial sequence rather than a stack of status cards.

You do not need to follow every inner step. First name the small job, then look at what was checked, then choose to continue, ask for a correction, or stop.

What stays visible

Work boundary
The small part of the job this run is allowed to touch.
Proof
What was checked before anyone asks you to move on.
Your decision
You can approve, ask for a correction, or leave the work manually.

Four proof points

  1. 01 / Boundary

    Name the work before it spreads

    Start with one small job and say what it may touch. That makes the next choice easier to see.

  2. 02 / Packet

    Keep the same facts together

    Put the goal, the limits, and the checked result in one note you can read.

  3. 03 / Proof

    Show what was observed

    See what happened before anyone asks you to go on.

  4. 04 / Exit

    Keep a manual way out

    You can pause, look again, or stop instead of being pushed through the next step.

Before / After: the same packet

The same case material is shown before and after it is arranged in a readable packet.

Same case packet

Before

  • Goal appears in one reply
  • Limit is buried in another
  • Proof arrives late
  • Decision waits for a manual search

After

  • Boundary is named once
  • Relevant facts travel together
  • Observed proof is marked
  • Human decision remains explicit

Human review remains outside the packet

The information does not become more certain by being rearranged; the packet simply makes its boundary, proof, and next decision easier to inspect.The same note is easier to read when the important parts are kept together.
Text equivalent
  1. Before: replies, limits, and pending questions are separated.
  2. After: one packet holds the boundary, observed proof, unresolved risk, and human decision.

A route that stays inspectable

Context Packet Routing

Dwi does not replace platform safeguards. It adds an editorial view of bounded context, staged proof, and the human decision that remains outside automation.

Context Packet Routing

Relevant inputs enter one packet on neutral routes, move through review on a solid observed route, and keep correction and manual exit visibly separate.

Swipe the diagram to follow the route.

Human goalExisting factsWorking limitsContext packet{ }Human reviewApproved nextstep{ }Manual exitinputobserved / approvedproposed / retryhuman-controlled exit
  • Orange-red { }: human scope, contract, or gate
  • Light-gray •: packet or checkpoint
  • Solid graphite route: observed or approved
  • Dashed graphite route: proposed or retry
  • Neutral route: relevant input
  • Orange route: human-controlled exit
Routes communicate state as well as direction: neutral is input, solid is observed or approved, dashed is proposed or a retry, and orange remains a human-controlled exit.Only the information needed for this job goes into one note before you look at it.
Text equivalent
  1. Human goal, existing facts, and working limits enter a single context packet.
  2. The packet moves to human review on an observed route.
  3. An approved route proceeds to the next bounded step.
  4. A proposed correction and a human-controlled manual exit remain visibly separate.

Four Cells, one Scheduler

Exactly four cells work inside separate roles while one scheduler coordinates their resource windows.

Swipe the diagram to inspect all four cells.

Cell 01Cell 02Cell 03Cell 04Scheduler
  1. Cell 01Gather bounded material
  2. Cell 02Clarify assumptions
  3. Cell 03Check risk and proof
  4. Cell 04Prepare review note
  5. SchedulerCoordinates resource windows for the four cells
Cells do not replace human authority. The scheduler coordinates work; the root gate still makes the final decision.Four small jobs are easier to follow than one large, unclear job. A scheduler keeps them in order.
Text equivalent
  1. Cell one gathers the bounded materials.
  2. Cell two normalizes assumptions.
  3. Cell three checks risk and evidence.
  4. Cell four prepares the review note.
  5. One scheduler coordinates resource windows across all four cells.

Observed route with a bounded correction loop

Spark moves to Integrate, then Independent Audit, then Root Gate. A dashed correction loop may return to integration at most twice.

Swipe the diagram to follow every stage.

Sparkbegin bounded workIntegratecombine stagedoutputIndependentAuditcheck evidence andrisk{ }Root Gatehuman finaldecisionCorrection loop ×2human gate
  • Orange-red { }: human contract or gate
  • Light-gray •: checkpoint
  • Solid graphite route: observed or approved
  • Dashed graphite route: proposed correction
The correction loop is visibly limited to two passes. The orange-red root gate remains a human decision point.The work moves through four clear stops. If something is wrong, it can go back for a small correction twice, then you look again.
Text equivalent
  1. Spark begins one bounded piece of work.
  2. Integrate combines the staged output.
  3. Independent Audit checks the evidence and risk.
  4. Root Gate remains the human final decision.
  5. A proposed correction may loop from audit to integration no more than two times.

One case: measured wall time

Proportional evidence from one bounded case

Proportional evidence from one bounded case

Measured wall time is 1,930 seconds before and 1,176 seconds after in one case. The difference is 754 seconds, about 39 percent. Context reuse is 94.5 percent and effective-new context is 5.5 percent.

One case: measured wall time

Before1,930 seconds
After1,176 seconds

Difference in this case

754 secondsabout 39%

One measured case only — descriptive evidence, not a causal claim or a universal benchmark.

These values describe one measured case. They do not establish a cause or promise the same result elsewhere.This is one timed example. It shows what was measured here, not what will happen every time.
Text equivalent
  1. One case: measured wall time was 1,930 seconds before and 1,176 seconds after.
  2. The difference in this case was 754 seconds, about 39 percent.
  3. Context reuse was 94.5 percent; effective-new context was 5.5 percent.
  4. The figures are descriptive, not a causal claim or universal benchmark.

Six entry modules

Six entry modules

Each module helps you make one part of the work easier to see before you choose the next step.

  1. 01

    Conduct

    Turn a conversation into an ordered next step.

  2. 02

    Lean

    Remove a step that does not help you decide.

  3. 03

    Budget

    See how much work the current run is using.

  4. 04

    Bridge

    Keep notes from different places together.

  5. 05

    Arc

    Keep a clear place to pause and check again.

  6. 06

    Evidence

    Keep the check beside the decision it supports.

The decision stays human

The decision stays human

The workflow can be bounded and the proof can be staged without removing the person who decides whether work continues.

Safety / Manual Exit

When material risk is unresolved, escalation pauses and the case returns to human review. The platform's documented stop control remains available for a manual exit.

Swipe the diagram to follow the manual exit.

Material riskunresolved{ }Pause escalation{ }Return to humanreview{ }Manual exitKeep the platform's documented stop controlavailable
  • Orange-red { }: human review and manual exit
  • Light-gray •: checkpoint
  • Solid graphite route: observed route
  • Orange route: human-controlled manual exit
Manual exit is a visible route, not a hidden failure state. It remains available beside the staged workflow.If something important is still unclear, pause. Look at it with a person before you continue or stop.
Text equivalent
  1. An unresolved material risk pauses escalation.
  2. The case returns to human review.
  3. The platform's documented stop control remains available.
  4. A person can take the manual exit.