Trellvix
Decision trace
Trust

Every outbound action. Every piece of your data involved.

Not a log buried in settings. A sealed, append-only record of what left this machine, who received it, why, and what was deliberately withheld.

See what it holds to
trellvix.work / nova · traceLive
TRACE LEDGER Today - 20 entries, 3 external tools touched No HELD over 24h ✓ TIME ACTION DATA CARRIED BOUNDARY OUTCOME 10:42 Brave Search · Delaware filing deadline Query: DE state corporate annual report due 2025 Public search data only Nothing personal, nothing about you Read-only · no send Default boundary ● OK 11:08 Read email · investor reply from S Re: Q3 update - review requested + 2 questions Subject, sender, body Held in memory, not forwarded Read-only · inbox scope Default boundary ● OK 11:26 Draft · investor update 289 words produced locally · 3 numbers from memory $382k, Acme renewal date, Priya name Carried from memory into draft NOT SENT · awaiting approval Approval boundary ● HELD 11:41 Calendar hold · leadership review Thursday 3pm · 60min · blocked 4 attendees Names, 60min slot, tentative flag Tentative only Read & tentative write Calendar scope only ● OK 12:04 Reminder set · Thu 9am - vendor quote chase Only fires if 2 quotes not returned by 8:55 AM 2 vendor names, 1 due date Queued locally, no send yet Not fired yet Default boundary ◷ PENDING

Decision trace

Not a log buried in settings. A sealed, append-only record of what left this machine, who received it, why, and what was deliberately withheld.

What holds

Per field: Not per policyWithheld: Recorded beside what wentOrder: Hash-sealed, append-onlyRetention: What they keep, or unknownTurns: Conversation counted too

The difference

A privacy policy says what could happen. This says what did.

Every departure is written before it leaves and chained to the one before it, so the order cannot be rewritten quietly - which is a stronger guarantee than a git branch, because a branch can be forced. (egress.ts, store.ts)

01

What went, field by field

Not "contacted a supplier". Your name and the order reference, and nothing else, itemised.

02

What was held back

The honest half of the same record. A field withheld is recorded beside the fields that travelled, because a list of what went is only half an answer.

03

What they do with it afterwards

None, unknown, or retains - and "unknown" is its own answer rather than being rounded down to "none".

04

How much conversation travelled

A different kind of disclosure from a field, so it is counted separately rather than folded in.

How it goes

From declaration to record, in four moves.

01

It declares before it goes

A parcel names its fields up front. Anything undeclared cannot be in it.

02

The gate reads the declaration

Minimal disclosure is enforced against that list, not against intent.

03

The trip is written down

Sealed into the chain, with the destination, the purpose, and the fields.

04

You read it whenever you like

In the command centre, under "Data out".

Before anything leaves

An empty record is a claim in itself. It means nothing has left.

This ledger does not start with a summary of what might happen. It starts empty and grows only when something actually crosses the boundary, which is what makes a line in it worth reading.

Nothing has left this machine

Every outbound message, lookup and call is written here with the exact fields that went and who received them. There is nothing to show yet.

What it holds to

Four things the record will never do. Including for us.

01

It never says "contacted a vendor"

That is a summary, and a summary is where the detail you needed goes missing.

02

It never edits an entry

Append-only, and each entry sealed against the last. Correction is a new line, never a rewrite.

03

It never omits a refusal

What it declined to do is its own section. An agent whose refusals are invisible is indistinguishable from one that never refuses.

04

It never leaves you guessing

If something went out, it is in the record. If nothing did, that is what the record says.

The rest of the workbench.

Approvals

Decisions arrive with the work done, not the questions still open.

Memory

Context that stays warm after the meeting, the email, and the tab close.

Meet the chief of staff your company never had.

See how it works