CONTRACT WRITING SYSTEM

SI-CWS

A contract writing system built for Super Intelligence (SI) assistance from the start, and built to integrate natively with AcqBot.

HOW IT WORKS

From requirement to signed record

An agent can draft, check and propose through the registry. It cannot take the actions below.
SI-CWS · STANDALONE AUTHORIZATION BOUNDARYOIDC · APIAcqBotrequirementsTool registryone definitionper capabilityREST / OpenAPIMCPUIEvalsInstrumentvalidated at entryClause engineproof tracesEXPLAINSACEDoW clause recordRenderPDF/A + PDS
HUMAN-ONLY ACTIONSSignObligateReleasePostTransmit
Clause engine
A deterministic rule interpreter explains why each clause applies with a proof trace, and blocks release when a required clause is missing.Select any box in the diagram to see what it does.

WHY IT MATTERS

Contract writing is due for a rebuild

Federal contracting runs on a patchwork. PD2 is still in service for the Navy and defense agencies, and the newer service systems share one baseline and report merge pain. SI-CWS is built to replace the DoW programs of record: PD2/SPS, Army ACWS, Air Force CON-IT and Navy ePS.

BUILT-IN CHECKS

What every contract has to pass

Fields are checked as they are written, not at release, and every validation message comes with help text.
VALIDATIONILLUSTRATIVE
Delivery datemissing
Helpadd a date for each line item
Funding linecomplete

ILLUSTRATIVE WALKTHROUGH

Watch a contract get written

Scroll through one sample contract action, from requirement to release. Records and clause numbers are illustrative.

01A requirement arrives
A requirement and its market research hand off from AcqBot through the event outbox, and a new draft opens at revision 1.
02The instrument takes shape
Line items and funding are assembled into one instrument. An agent drafts on behalf of a named human, and every change is audited.
03Clauses, with reasons
The draft is registered with the clause engine. Each recommended clause comes back with the rule and facts that made it apply.
04Compliance checks
Problems are caught at entry with help text, and release stays blocked until every required check passes.
05Reviewed, signed, released
The agent can propose release, but only the contracting officer can sign. The review document records who did what.
Requirement
Instrument
Clauses
Checks
Release
SI-CWS/ IntakeILLUSTRATIVE
Requirement intake · REQ-0000-0217
from AcqBot · event outboxnew
RequirementREQ-0000-0217
TitleSample cloud hosting services
Estimated value$1,200,000.00 (sample)
Organizationagency-sample
Attached
✓Market research reportMR-0000-12
✓Independent cost estimateIGCE-0000-04
Draft created
DRAFTSTATUSREVISION
DRF-0000-0031draft1

KEY CAPABILITIES

What SI-CWS is built to do

Each phase ends with a real document, PDS-valid and reviewed by a contracting officer.

0capabilities in the requirements register
0rows in the PD2 parity checklist
0agent-ready requirements
0P0 spikes to retire key risks
PD2 parity, trackedA row-by-row checklist against PD2.
Delivery date
Help text shown with every message
Validated at entryErrors are caught as you type.
52.2XX-01 Sample clausewhy: rule R-000 matched
Clauses with reasonsEach clause shows why it applies.
registry
REST / OpenAPI
MCP
UI
Evals
One tool registryAPI, MCP, UI and evals from one definition.
Draftagent ✓
Signhuman only 🔒
Releasehuman only 🔒
Agents propose, humans decideFive actions stay human-only.
AcqBot · REQ-0000→SI-CWS · draft contract action
Native to AcqBotRequirements arrive ready to write.
Counts from the SI-CWS requirements register, PD2 parity checklist and development plan. Example data in the cards is illustrative.

WHO IT IS FOR

Built for DoW and federal agency contracting offices

Service-neutral by design. Differences between components are configuration overlays on one codebase, not forks.

Contracting officers and specialists

The people who write, review, sign and release awards and modifications.

Agreements officers

Parity scope includes non-FAR instruments such as other transactions and grants.

Requirements and program teams

Teams already working in AcqBot, whose requirements and market research carry straight into the contract action.

Planning your next contract writing system?

If your contracting office is looking ahead, we would like to hear from you.