Commitment & outcome accountability
Track supplier deliveries, contractor milestones, repayments, reimbursements and other commitments. OUTCOME connects what was agreed to reviewed evidence, shows what is outstanding, and makes the next decision clear.
No account is required to explore the product. Signing in names a personal workspace. It does not authorise a payment.
The promise, the delivery, and the amount someone asks to release stop matching. A shortfall can still be presented as the original figure. The people responsible are left reconstructing the story from inboxes and spreadsheets.
OUTCOME keeps what was agreed, the evidence of what happened, the exposure when they differ, and the decision that follows. A supplier order, a milestone, a repayment, a reimbursement, an expense, or an escrow-style release uses the same record. The 50-carton example shows the record. It is not the boundary of the product.
When money depends on work being completed, delivered, repaid or evidenced, someone has to keep the agreement and the outcome aligned. OUTCOME gives that person one place to see the obligation, the proof and the decision still waiting to be made.
Compare what was ordered or promised with what has actually been verified.
Keep each deliverable, review and release condition tied to the original agreement.
Understand what is due, what is supported by evidence and what still needs a human decision.
A spreadsheet can store a number. An inbox can store a message. OUTCOME connects the original commitment to reviewed evidence, a transparent assessment and the human decision that follows—without pretending that a recommendation or signature is a completed payment.
Terms and amendments remain part of the same record.
Evidence has a review state; an unreviewed note is not treated as verified.
See why an action is recommended and what still requires a person.
You can see the evidence behind a conclusion. A person approves consequential steps. An explanation is an interpretation, and it never authorises a payment. An approval is recorded as APPROVED — NOT SUBMITTED unless a completed transfer exists. Only a completed transfer may be called paid.
The public audit trail, including what is and is not written on chain, lives in Security and trust. It does not sit in the way of the work.
Get started to sign in and open your own workspace, or look around the labelled sample first. Nothing on this page moves money.
Acme Supplies is a labelled sample. Fifty cartons were agreed, forty-two were verified as received, and the original release stays blocked. A milestone or a repayment uses this same record.
Open a record to see what was agreed, what the evidence shows, and the recommended next step.
Open a record to review its status, evidence and the next decision.
Repeated, verified discrepancies for the same other party. A supplier shortfall is one example. Patterns need at least two verified incidents. They are review signals, not findings of misconduct.
Describe what happened in ordinary language, or enter the fields yourself. Nothing is saved until you confirm an extraction or submit the form.
Checking whether ordinary-language extraction is available.
Security and trust
This page is for people who want the public audit detail. It does not change a commitment, and connecting a wallet here does not authorise a payment.
A recommendation is not an approval. An approval is recorded as APPROVED — NOT SUBMITTED unless a real transfer exists. Only a completed transfer may be called paid, and only with the network, the transaction hash, and an explorer link checked against the chain. This application has not recorded a completed transfer.
Signing in names a personal workspace. Signing an audit record writes a hash. Neither action submits a payment.
The live contract is thewordweaver.testnet. The policy is any_account. Code hash 5UNnZ4KvwoCxHt5ADhJnkCchP2h1xR6fnCXPP8c1rgpr. Upgrade FNzw1EPWRwepL2Bni1XH9Wz2nWJyqxeV4tPCpS5joXrc is FINAL.
Checking the live audit policy.
Event 1, stored id OUTCOME-DEMO-PO-104, is the owner event and survived the upgrade. record_event 3N8VVzFr3QLm6iJKvS2twM4VxCWZyrec9FfqP2zNb2kj is FINAL. It is not the sample order’s digest.
A later non-owner record_event from nocgykc7.thewordweaver.testnet is also FINAL as sequence 2 (7ZXWXUjPtWFQiYG6FKH91WimEmQWMwibSRoxifeweHk3). It was not filed through the app’s sign button and is not the sample order’s digest.
Earlier test records shown above were not filed through this app sign flow. The selected commitment’s receipt appears below only after OUTCOME verifies a matching transaction payload.
A digest that is not on chain is described as not written on chain. Open a commitment to see that order’s digest.
An operational brief or an ordinary-language extraction is shown only after the cryptographic checks pass. HTTPS is not attestation. A failed check is not shown as verified. The deterministic assessment and a person’s approval remain authoritative. A brief never authorises a payment.
Before a brief is shown, OUTCOME preflights an UpToDate Intel TDX quote (debug bit clear, signing address and nonce bound, MRCONFIGID and RTMR3 checked) and then checks the EIP-191 ECDSA signature over the exact response bytes. A provider-TEE signature also requires an NVIDIA NRAS verdict of boolean true and a matching eat_nonce. A gateway signature is labelled separately and does not claim the model quote signed those bytes. Verification fails closed. The NRAS JWT signature, Sigstore provenance, and the live TLS peer certificate are not verified here.