THE NO-ADVICE BOUNDARY
What TaxRiskOS does — and where it stops
TaxRiskOS organizes the first hour of an IRS notice: intake, deadline, document checklist, escalation flag, and a handoff packet. The legal Law, Analysis, and Conclusion are left for the licensed professional — visibly, on purpose.
Workflow support only. Not legal or tax advice. No response drafting.
Two columns, one line
Everything TaxRiskOS produces is workflow structure around a notice. Everything that requires professional judgment is left to the professional. The list on the left is what the software emits; the list on the right is what stays with you.
What TaxRiskOS does
- Captures the notice facts the practitioner confirms
- Computes the response deadline by rule from the notice date
- Assembles a document checklist for that notice type
- Surfaces an escalation flag (a routing label, not a conclusion)
- Builds a facts-only handoff packet with the analysis left blank
- Keeps a time-stamped audit trail of the session
What TaxRiskOS does not do
- Does not state what the notice means for this taxpayer
- Does not apply law to facts or analyze the position
- Does not draft IRS or state responses
- Does not represent taxpayers
- Does not fill the Law, Analysis, or Conclusion fields
- Does not replace CPA, EA, or attorney judgment
The handoff, drawn out
A counsel handoff has four parts. TaxRiskOS fills exactly one of them — the Facts — from the intake the practitioner confirmed. The other three are left open and labeled, so the boundary is something you can see rather than something you have to trust.
Facts auto-filled
- Matter: Sample Taxpayer LLC — CP2000 dated 2023-09-18
- Deadline: 2023-10-18 (notice date + 30-day response window)
- On file: filed Form 1120-S, brokerage 1099 composite
- Still needed: cost-basis records for the flagged securities
- Escalation flag: L3 — manager review (routing label only)
Law left blank
Left for the licensed professional. TaxRiskOS does not write this.
Analysis left blank
Left for the licensed professional. TaxRiskOS does not write this.
Conclusion left blank
Left for the licensed professional. TaxRiskOS does not write this.
The packet assembles facts and stops. The Law, Analysis, and Conclusion are the professional's — the software has no path that writes them.
What it emits · what stays with you
The same split, itemized. Each emitted artifact is workflow structure — a label, a date, a list. Each retained item is judgment the licensed professional keeps.
TaxRiskOS emits
- Notice factstype, date, tax period, form referenced, amount asserted — captured as the practitioner confirms them.
- A deadline, computed by rulenotice date plus the response window — the same notice and date always produce the same date.
- A document checklistthe records typically associated with that notice type, as a gather/still-needed list.
- An escalation flaga routing label (L1–L5) that surfaces who should look at the matter. A label, not a determination.
- A facts-only handoff packetthe confirmed facts assembled for review — with Law, Analysis, and Conclusion left blank.
- An ordered audit traila time-stamped record of what was captured and when. It documents process, not advice.
Left for the licensed professional
- The legal conclusionwhat the notice means for this taxpayer and what position to take is the professional's call.
- The analysisapplying authority to the facts is judgment work the software does not perform.
- The response strategyTaxRiskOS does not draft IRS or state responses and does not represent taxpayers.
- Whether to escalatethe routing flag is an input to the professional's decision, never a substitute for it.
- Every inputthe practitioner confirms the notice type, date, deadline, and documents before anything is assembled.
- The final judgmentthe product augments the first-hour workflow; the licensed professional remains responsible.
How the boundary is held in the output
Two descriptive facts about how the software is built — stated as design, not as a claim about results.
- One rule-based path. Intake, deadline, checklist, flag, and packet are produced by fixed rules — the same notice yields the same structure, with no generative model in the decision path. There is no step that forms a legal conclusion.
- A no-advice check on every output. Each practitioner-facing string is generated through a single output path that screens for advice-style language before it is shown. A string that does not clear the check is not emitted.
- The analysis fields are never populated. The handoff template carries Law, Analysis, and Conclusion as labeled-blank slots. The generator fills Facts and leaves the rest for the professional.
- The practitioner confirms the inputs. Notice type, date, deadline, and documents are user-confirmed; the workflow organizes them, it does not decide them.
Questions about the boundary
Why are the Law, Analysis, and Conclusion fields blank?
Because filling them would be legal or tax analysis, and TaxRiskOS does not do that. The handoff packet assembles the confirmed facts and stops at the boundary. The blank fields are a deliberate handoff marker — the licensed professional writes them.
Is the blank handoff just an empty document?
No. The Facts block is fully assembled from the practitioner-confirmed intake — matter, deadline, documents on file, and documents still needed. Only the analysis fields are left open, and they are labeled as left for the professional rather than silently omitted.
How does the software keep advice out of its output?
Every practitioner-facing string is generated through a single output path that applies a no-advice boundary check before anything is shown. The check screens for advice-style language; a string that does not clear it is not emitted. The intent is structural: the workflow has no path that produces a legal conclusion.
Does the escalation flag tell me what to do?
No. The flag is a rule-based routing label — the same notice always yields the same flag — that surfaces whether a matter looks like associate-level screening or a partner/counsel review. It is a workflow signal, not a legal or tax conclusion, and the professional decides what to do with it.
Is any of this AI?
V1 keeps no generative model in the production decision path. AI may be used internally to build and test the software, but not to produce the practitioner-facing intake, deadline, checklist, flag, or packet.