Skip to main content
DraftCounsel™

DraftCounsel · Reference · release 2026.11.16

Draft desk: capabilities and limits

A grounded first draft assembled from real exemplars and the clause library, with every election left to the attorney.

The desk itself lives at /workspace/draft (launcher: /draft). Nothing on this page changes what the desk does; it describes it, dated by the release that generated it.

A walkthrough (fictional)

Fictional matter — demonstration: Invented names and facts; nothing here is a real client, party, court or filing.

Every name, party, court and matter below is invented for illustration.

  1. The invented reviewing attorney at Harrow & Vale LLP chooses a Mutual NDA under Florida law, names Meridian Data Systems, LLC and Harbor Analytics, Inc., and answers the questionnaire; an answer can be marked unknown.
  2. Where the clause library covers the instrument the operative text is assembled deterministically; where it does not, the grounded lane drafts from five pinned exemplars and labels the draft as statute-cited.
  3. Contradictory facts (the same person as landlord and guarantor) are flagged before assembly; a missing required fact stops the draft and names the key.
  4. The draft opens in the workspace for revision; the execution-formalities appendix travels with the export.

Mechanisms

  • The clause library and state packs for the covered instruments; the grounded lane for the rest.
  • The required-facts and conflict gates before assembly.
  • The dual-engine program on request: two independent passes on the same pinned exemplars, reconciled with the divergences shown.
  • The rigor label computed from the code path that ran.

Limits

  • No governing state, no draft.
  • A document with no lawful exemplar lane and no library coverage is refused.
  • The draft is not for execution until the supervising attorney finalizes it.

Always stops for a person (the autonomy floor)

  • Nothing is sent to anyone outside the platform without a person choosing to send it. (minimum: person)
  • No share link leaves without a person minting it for a named recipient. (minimum: person)
  • No artifact is finalized without an attorney’s recorded decision on its exact version. (minimum: attorney)
  • No final packet or external delivery leaves without an attorney’s approval and the export gate. (minimum: attorney)
  • Nothing is deleted without a person confirming the deletion; legal holds refuse it outright. (minimum: person)
  • A matter’s state (open, closed, on hold, archived) changes only when a person changes it. (minimum: person)

What this desk refuses

From the refusals catalogue (57 rows apply); the full catalogue is at /refusals.

  • Drafting without a valid governing state.

    Choose the governing state before drafting.

  • A "deterministic" label on a document the clause library does not cover.

    The draft proceeds on the grounded lane with the honest label.

  • Claiming a verified, state-exact document before the supervising attorney signs off.

    The attorney verifies statutory references against official sources and finalizes.

  • Entering the attorney engines without the licensed-attorney attestation, the conflict answers and every acknowledgment.

    Complete the attestation and the conflict screen; a flagged conflict is resolved by the attorney, not the software.

  • Running a paid desk without an active session, a trial allotment or a covering purchase.

    Sign in, use the trial allotment, or purchase the matter.

  • An estate instrument exported without its state execution-formalities appendix.

    Name the governing state; the appendix is generated from the cited rule.

  • Assembling an instrument while a mandatory intake fact is missing.

    Supply every required fact named in the report.

  • An instrument naming the same person in roles that must differ.

    Correct the roles; the gate compares case- and space-insensitively.

  • Representation of any kind: filing, service, negotiation with a party, or appearance, for anyone.

    A licensed attorney represents; the platform prepares.

  • Drafting, reviewing or redlining a document for which no lawful exemplar lane is live.

    Choose a document type with a lane, or wait on the named owner item (a keyed connector or a reviewed pack).

  • Output that lifts verbatim runs, or too much scattered overlap, from the exemplar filings.

    The run is refused and reported; the engine drafts afresh on the same pinned exemplars.

  • Output that carries the exemplar filings' party names into the matter.

    The run is refused and reported; the attorney never sees a foreign party in the draft.

  • A dual-engine consensus that swallows a material disagreement between the engines, or names it without binding a disposition to its issue id (a missing, duplicated or unknown id, a bare marker, or a conflict marked decided).

    The divergence is carried as a decision card bound to its issue id; the attorney adjudicates it.

  • Delivering single-engine output when a dual run was purchased and one engine failed.

    Retry, or run the standard lane knowingly.

  • Predicting an outcome, a ruling or a bench's decision.

    The passage is flagged for the attorney; the War Room prepares questions, it never forecasts.

  • Grounding a matter on a same-named county of another state.

    The matter's own county tops the ladder; the run searches when the lane is thin.

  • Reaching a matter, review, draft, comparison or governed version that belongs to another tenant, or through a removed membership.

    Work inside an active membership of the matter's tenant.

  • Reaching a matter the user is screened from, on any surface, including background execution.

    The firm lifts the wall in the record; authorized colleagues keep their work.

  • Sending a byte to a vendor outside the permitted list, over a non-https scheme, to a private network, or with a data class the vendor is not cleared for.

    The owner reviews the constant; the surface reports the refusal instead of substituting a vendor.

  • A request path carrying a literal or encoded backslash, an invalid escape, double encoding or a control character.

    Request the route as published.

  • A dual-engine run whose second provider is missing, disallowed, or times out mid-run.

    The typed failure carries the partial stage receipt (which branch ran, which did not, why); the fee was charged once at most; the attorney may separately elect a single-engine tier.

  • A request to resume a long draft whose completeness state reads complete (no pending sections).

    Edit the document directly, or run a new draft; the completeness state on the record says what is pending.

  • A workflow requested for a state or task the coverage registry does not list as supported.

    Use the workflow in a supported state, or the owner adds the state to the registry with its rights, version, evaluated output and owner first.

  • A decision packet with a missing or unrecognized schema version on its envelope or any manifest, an unknown field, or missing required evidence.

    Issue the packet again from the platform; the validator names each defect.

  • GET /api/verify/lookup answers no-record for every digest.

    The owner decides the anchoring service; offline verification on /verify needs no lookup at all.

  • A component whose bounded probe did not answer reads unknown on /status and /api/status, never operational.

    Wait for the next probe, or read the component's configuration and readiness columns, which are separate from the probe.

  • A vitals beacon carrying anything beyond the six coarse fields (route pattern, metric, value, device class, connection class, deployment id).

    Nothing to do: the beacon the platform ships sends only the six fields.

  • A personal voice profile that drops a firm prohibition or a protected rule.

    Keep the personal profile to terminology and style; a firm owner changes a prohibition through a new playbook version.

  • A write that carries a stale version fence, or a write by someone who does not hold the pen.

    Re-read the current version, re-apply the change and write with the current fence; or wait for the pen.

  • Treating an owner, an admin or any role as a licensed attorney without an attested record with a bar identifier and a jurisdiction, or advertising an attested record as verified.

    A firm owner records the attestation with the bar identifier and the jurisdiction; the record then reads attested, not verified.

  • A stored firm instruction that names or weakens a locked prompt (the injection guard, the UPL lint, the privilege and client-facing guardrails, the OCP standing orders, the dual-engine synthesis), or an instruction of a kind outside the permitted list.

    Keep firm instructions to the house voice, terminology, formatting, the signature block and jurisdiction preferences.

  • Sending, sharing externally, finalizing, exporting a final packet, deleting or changing a matter's state without a person confirming that act, or confirming more than one such act in one approval, or a firm setting that lowers the floor.

    Confirm each act on its own; raise the firm's confirmation level if the firm wants a second reviewer.

  • Serving a privileged document on an API key, or reaching a matter outside owner ∪ firm partition − screens ∩ allow-list.

    Read the document as the attorney on the desk; the key reads ordinary and client-producible material only.

  • Minting, returning or accepting a confirmation token through the API, MCP, batch or any cancellation path; executing anything beyond a proposal.

    Propose through the door; an attorney accepts the proposal to the rail on the desk, where the full gate stack runs.

  • Reporting a read as verified when any item in it is weaker, or reporting an unread table as empty.

    Read the per-item statuses and the read_state; an unreadable read is retried or escalated, never treated as empty.

  • Answering a faulted read with an empty 200, or a failed check with a pass.

    Retry after the store recovers; the response names the fault.

  • A webhook payload carrying content (text, a body, a quote, a title, a name), a log line, or a delivery to a private-network or non-https target.

    Resolve the pointer through the API; register an https target on a public host.

  • A connector whose registry entry reads planned or pilot presented as connected, syncing or live anywhere.

    Use the export and compose-link paths that are live today; the owner activates a connector on confirmed demand.

  • A retry that would re-send a done operation, or an operation whose other side answers a different matter than the recorded mapping.

    A firm member corrects the mapping by name; the operation is re-queued only then.

  • Treating a passed biometric on the phone as server authorization, or extending a revoked session because the shell unlocked, or placing anything privileged on a lock screen or in a notification.

    Sign in again; the shell opens but the desk waits for the server.

  • Deleting a matter, an account or a firm while a legal hold covers it.

    The attorney or the owner releases the hold by name when it ends; the deletion then runs and produces its receipt.

  • Placing a legal hold without a reason or without a review date within a year.

    Place the hold with its reason and a review date, and review it on that date.

  • Serving a restored database before the later ledgers are re-applied: a deleted row, a revoked share, key or grant, a superseded approval, or a job that would resume by itself.

    Apply the post-restore actions and pass the verification; interrupted jobs are re-run only by a person.

  • A removed user reading, launching work or acting through a connector; identity recovery restoring more than the sign-in.

    A firm administrator re-adds the member by name; a connector the user connected is taken over by name or revoked.

  • A procurement, trust or lifecycle document claiming a certification the platform does not hold (SOC 2 certified or compliant, HIPAA compliant, bank-grade and the like).

    Read the controls with their evidence in the procurement package; a certification appears only after its report exists.

  • A published accuracy or outcome percentage without its count and denominator, or over a denominator too small to carry it.

    Read the count and the denominator; the percentage appears when the denominator can carry it.

  • A claim that the platform outperforms a named competitor without a matched, blinded study on the same matters with its method published.

    Compare what each product publishes; the benchmark reports this platform on its own terms.

  • Adopting or advertising an upgrade as better on fewer than twenty blind, versioned pairs, on an unmet margin, or with a serious regression.

    Run more blind pairs; keep the preserved baseline in service meanwhile.

  • Selling a matter, a tier or an upgrade before the purchase-to-approved-export acceptance passed in controlled accounts.

    Evaluate on the sample matter; purchases open when the owner records the acceptance and the activation.

  • A second grant, a second delivery or a revived benefit from a duplicate, reordered or post-refund event.

    Support reconciles a quarantined purchase by hand from the provider record.

  • A saving, a return on investment or a projection presented as unit economics, or a price changed from the economics module.

    Read the observed cost per accepted deliverable with its counts.

  • Opening the accounts door before the SMTP proof and the Auth switches, opening commerce before the acceptance, or treating the activation record as approved without the owner.

    The owner reviews the record, chooses the cohorts and approves it by name.

  • Counting a configuration check, a keyless run that stops at the transport, or a DraftBench skip as live proof of a program.

    The owner runs npm run live-proof with the keys in a session shell and commits the receipts.

  • A positioning statement that ranks, uses a superlative or disparages another product.

    Read the positioning facts with their evidence and qualifications.

  • Building trust accounting, outcome prediction, deposition capture hardware, a public marketing-domain intake form, an in-house e-signature system or an autonomous litigation agent; or deleting a function because an expansion was declined.

    Use the bounded answers: connectors, proposals only, the attorney-lane intake link, DocuSign under the firm’s credentials.

  • Grounding a Rule 2004 examination motion on the district courts' filings.

    Draft the motion on the record lane; it chooses the bankruptcy courts itself.

  • Reading a pinned official form from its publisher's site while drafting.

    When the Court revises a form, re-pin it on the forms desk's pin list, then rebuild its snapshot with the snapshot script's --only flag.

Inputs

  • The document type, governing state and questionnaire answers (an answer may be marked unknown; a required fact stays required)
  • Optional attachments the run accounts for by name
  • The purchased matter, carried in the link and the browser context from the last desk

Outputs

  • The draft with its rigor label and the exemplar provenance
  • The candor report (untracked citations, prediction language)
  • Word and PDF exports with the execution appendix

DraftCounsel is professional drafting software for licensed attorneys, operated by LegalDraft Technologies LLC. DraftCounsel is not a law firm and does not provide legal advice. All output is AI-generated draft work product offered for attorney review; the supervising attorney is solely responsible for reviewing, revising, approving, and using any work product, and for compliance with applicable rules of professional conduct. Communications with DraftCounsel are not protected by attorney-client privilege.