EVD-01 · Witness Rollout · In PKG-A Land, PKG-B Prove
A recorder on every agent, and it stays on.
Witness on every agent harness and every machine, kept recording when apps rewrite their configs.
Price
ScopedA fixed price in writing after a 30-minute call.
TermSet in the SOW
Runs inYour machines and your identity provider
Reply within 1 business day · The call is with Al Sharma
You need this if
01
Agents and coding assistants run on many machines, and nothing records what they do.
02
A recorder was installed, but an app update switched it off and nobody noticed.
03
Audit asks who approved an agent, and the answer is a name in a chat thread.
What you get
01
Witness wrapped on every MCP client in scope.
02
A guard that re-wraps configs when an app rewrites them.
03
Nightly chain anchors and a check your team can run.
04
A plan for verified principals through your identity provider.
05
A runbook for adding the next machine.
How it runs
DAY 0
Scoping call
30 minutes under mutual NDA.
You receiveA written summary of the problem, same day.
DAY 5
Fixed-price SOW
Scope, price, dates and exclusions.
You receiveOne price that does not move without your signature.
EVERY FRIDAY
Delivery
In your repository and your cloud.
You receiveA status note: done, next, blocked.
LAST DAY
Readout and handover
One hour with your leadership.
You receiveEvery record, runbook and line of code.
See for yourself
Terms and limits
01
Scope, price and dates are fixed in the SOW before work starts.
02
Records, code and files stay in your environment, and they are yours after handover.
Goes well with
Start
A recorder on every agent, and it stays on.
hello@darkvectorcognition.ai
Reply within 1 business day · The call is with Al Sharma