Nishi Family › Compare › Sovereign Legal Practice: Documents, E-Sign and Client Portal

Nishi Compare · capabilities, evidence and delivery

Sovereign Legal Practice: Documents, E-Sign and Client Portal

Compare capabilities and delivery evidence. Source discovery, qualification, deployment and accepted outcomes are separate; an open contract names work still to verify.

Nishi vs DocuSign, Clio, NetDocuments and PandaDoc -- the Utah practice stack from open-a-Word-file to edited, merged, signed, tracked and client-visible, with the law-clerk desk (templates, staleness, court forms) as first-class rows

Overview

The purpose, declared position and evidence coverage of this domain. Source presence and completed acceptance are different measures.

Where we are. Measured 2026-08-18 against source, not recalled. The practice spine already runs as gated organs (matter and conflicts, trust IOLTA, billing, docketing, document assembly, e-sign envelope and consent ceremony, completion certificate, new-matter intake) and the office suite reads and writes Word (.docx) natively, writes tracked revisions and comments, versions every save append-only, shares by ReBAC and serves diffs. The client vault and mail portal are LIVE on the firm's own subdomains (admin.andelinwest.com, mail.andelinwest.com). What is NOT there is the connective tissue the firm asked for: no way to bring an existing Word or Google document INTO the browser editor, no firm-scoped office on the firm domain, no signing from a document version, the client portal handler built but unpromoted on loopback, no tracked-revision rendering, no field placement or signer links, no PDF writer, no identity-verification, RON or e-filing connector. Two of the field's four rivals ship all of that today; the sovereign stack has the harder halves (fail-closed assembly, hash-chained audit, legal-validity predicates, never-void wills, append-only history) and is missing the easy halves. Landed the same evening (2026-08-18): mail merge and ODT promoted and registered (LP2), and the clerk desk -- template registry with version CID and effective epoch, document lineage at assembly, and the staleness worklist -- live and gated 13 of 13 (LP6, LP7, LP8), so a revised clause now names every template and every client document built from the old text. Landed 2026-08-19: LP1 import and LP4 sign-from-version shipped in ONE health-checked deploy of nx_office_daemon (now fork-per-request, so the per-request mmap scratch of the office core is reclaimed by construction, and ONE binary serves N realm-bound instances for LP3) -- a genuine Microsoft Word document imported live on nishifamily.com/office with its original kept byte for byte and 67 spec lines, refused 403 without the consent box, sealed certificate with two chained signers; nx_office_import_sign_gate 28 of 28 GREEN live; nx_odt grew the spec verb so .odt uploads import. Measured cost at the same time: the sign's durable store commit took longer than the 15 s edge window twice at box load 22 (the artifact landed both times) where the profiled quiet-box figure is 129 ms -- the box's fsync latency, recorded as such, not the ceremony.

Where we need to go. Version 0.1 is the firm's sentence made true on the firm's own host: open a Word, Google-exported or ODF document in the browser, edit it as a new version, merge it against the matter record, sign it under a consent-gated ceremony, and see the work trail; this page on /compare is the roadmap and the firm's site carries only the firm's deliverables. Version 1.0 adds the client portal on the firm domain and the law-clerk desk: template registry, document lineage and template staleness, tracked revisions rendered, signer fields and links, co-editing wired, Word MERGEFIELD templates honoured. Version 2.0 is beyond DocuSign for a Utah practice: a sovereign PDF writer with PAdES-shaped signed output, a signer identity ladder up to government ID, a Utah 46-1-3.6 remote-notarization record, bulk send, the NDA-gated e-filing connector, court-forms staleness, and clause-grounded cite-or-abstain contract review measured against the Vals redlining bar.

The unit. 1 u = one measured session-leg. Calibration: the office and legal suite shipped one lib+cli+gate organ per leg on 2026-07-19 (nine organs over two days), the refs rung took about seven domains per seat-leg on 2026-08-18, and the compare migration on this page (54 rows, 30 refs, this plan) took one leg on 2026-08-18. Estimates recalibrate as each rung lands.

Cost to open, edit, merge and sign on the firm's host (0.1): 3.5 u. Through milestone L0. All four rungs landed (LP2 2026-08-18; LP1, LP3 and LP4 2026-08-19): the firm office instance is live at admin.andelinwest.com/office in closed mode over the andelinwest_docportal realm, with nx_office_closed_gate 16 of 16 GREEN re-run after the deploy. Milestone L0 is DONE.

Cost to the client portal plus the clerk desk (1.0): 15 u. Through milestone L1 cumulative (11.5 u of new work over L0). Template staleness is 2 u of the 11.5 and is the single most differentiating rung on the board -- no rival documents it -- which is why the ranker will place it early once L0 lands.

Cost to beyond DocuSign for a Utah practice (2.0): 30 u. Everything below. The PDF writer (3 u) and the e-filing connector (3 u, NDA-gated by the courts) are the long poles; RON needs a commissioned notary and an approved provider posture, which the plan records honestly as a sovereign record around a notary rather than a notary network.

Research bar. Vals Legal AI Report -- redlining is measured on AI legal assistants against a lawyer baseline on redlining, extraction, Q and A, summarization. Theirs: lawyers 79.7 percent, Harvey Assistant 59.4, Vincent AI 53.6 on redlining; Harvey 94.8 on document Q and A. Ours: our 'Contract review grounded on the clause library' watch: designed as clause-grounded cite-or-abstain because free-form AI redlining is measured below the lawyer.

Research bar. Stanford RegLab hallucination study is measured on share of legal research answers citing unsupported law in leading RAG products. Theirs: 17 percent and over 33 percent for two leading products. Ours: our /compare/legal cite-or-abstain lane and this page's AI review watch.

Research bar. Utah RON statute 46-1-3.6 (effective 2026-05-06) is measured on what a lawful remote notarization must record and satisfy. Theirs: Utah-located notary, sight-and-sound A/V, ID image, stored recording, personal-appearance satisfied. Ours: the ron_session watch's done-rule fields.

Research bar. Utah e-filing integration is measured on whether a filer may build its own connector. Theirs: yes under NDA, then an eFiling Integration Guide describing the API. Ours: the efl_submit watch's named unblock.

Research bar. NIST SP 800-63A-4 (final July 2025) is measured on identity proofing evidence strength, document validation, presentation-attack detection. Theirs: IAL1 to IAL3, FAIR/STRONG/SUPERIOR evidence, PAD required for remote biometrics. Ours: the government-ID leg of the sc_signer_idv watch.

Research bar. Utah Uniform Electronic Estate Planning Documents Act (H.B. 181, effective 2026-05-06) is measured on which non-testamentary instruments may be executed, notarized, witnessed and retained electronically. Theirs: trusts, trust powers, durable powers of attorney, directives, guardian nominations and disclaimers; electronic presence satisfies a presence rule; an authorized officer's electronic signature satisfies notarization; certified paper copy by affirmation; deeds and vehicle titles excluded [utah-hb181-ueepda] [natlawreview-ueepda]. Ours: the lr_exec_ladder, sc_witness_session and sc_paper_certify watches (LP23, LP24, LP26).

Research bar. Utah Notary Amendments (S.B. 139, effective 2026-05-06) is measured on what a remote notarization must establish and retain. Theirs: government photo ID or passport plus secondary authentication (dynamic knowledge-based or biometric), a secure electronic journal, 10-year retention of the journal and the recording [utah-sb139-notary-2026] [utah-r623-100-5]. Ours: the ron_session watch's identity and retention fields (LP17).

Research bar. Utah State-Endorsed Digital Identity (S.B. 275, effective 2026-05-06) and the browser Digital Credentials API is measured on whether a signer can prove identity from the wallet on the phone without handing over a card image. Theirs: selective disclosure, minimum attributes, a digital guardian, no tracking through presentations; Chrome 141 and Safari 26 ship the API [utah-sb275-sedi] [utah-sedi-guide] [chrome-dc-api] [webkit-dc-api]. Ours: the sc_idv_sedi watch (LP25).

Research bar. WCAG 2.2 level AA and NIST SP 800-63B-4 is measured on whether the mobile ceremony is usable by an elderly client on the phone they already hold, behind a phishing-resistant login. Theirs: 24 by 24 CSS pixel targets, no dragging, no redundant entry, accessible authentication; AAL2 with syncable passkeys [wcag22] [nist-800-63b-4]. Ours: the lpd_mobile_ceremony and pk_login watches (LP27, LP28).

Research bar. Utah Office of Legal Services Innovation sandbox is measured on whether a software-delivered estate service may operate as an authorized entity in Utah. Theirs: Phase 3, authorized to August 2027, technology-based providers admitted, end-of-life planning served [utah-olsi-sandbox]. Ours: the delivery posture of the portal: a firm's tool today, an authorized entity only if the operator applies.

Research bar. DocuSign eSignature, Identify and Notary (vendor product pages) is measured on the e-sign, bulk send, identity-verification and notary products every SIGN and PORTAL row is graded against, as mirrored vendor pages [@docusign-esign] [@docusign-idv] [@docusign-notary]. Theirs: UNPINNED -- a SaaS product with no public machine-readable release registry; declared, not pinned; the mirrored pages carry their content pins and access dates in legalpractice.refs and are re-read at the next admission sweep. Ours: the rival column codes on every SIGN row and the Best codes on field placement (LP10) and the mobile ceremony (LP27).

Latest recorded release

2026-10-08 · LP1

2026-10-07 the last two document rows that were graded here against the practice rivals, docx_read_text and docx_read_spec (every practice rival Yes, no discrimination on this board), moved home to /compare/unidoc and became @xrow references here (35971 to 35903 to the next receipt under CAS); of the nine document rows named on 2026-10-07, five are now references to unidoc or office (dx_to_html, odt_read_text, pf_to_html, of_save, nx_doc_serve_response earlier; docx_read_text, docx_read_spec now), three are @xrow office (dx_emit_track, dx_cm_add, pf_check), and the four watch rows that remain practice rows carry this board's own rungs: of_inline_runs and dx_patch_para (the beyond-Google-Docs round trip, LP12 class), dx_html_track (LP11, the read side of redlines for review without Word) and pf_defined_terms (LP22, the Litera class of proofing, practice-specific by nature). The first two are candidates to move home once unidoc declares the editor rungs; queued, not moved, because moving a watch row moves its rung and that is unidoc's RACI lane.

Release history and work log

Release entries describe recorded changes; they do not establish that every capability passed evaluation.

27 of 55 capability source symbols found|8 of them authored stronger-claims|28 open|coverage 490/1000|adoption 25 full / 2 partial

Evidence profile — what the gaps on this board actually are

Measured by nx_swcompare_evidence, read back by nx_evprofile_lib. Every figure is a count with its denominator — there is deliberately no score, no grade and no percentage anywhere in this band, because a stored scalar is a field a seat can edit and a counted partition is not.

proven able to fail counts the gates that have a RECORDED RED — nx_gate_bite mutated the gate subject, rebuilt it, watched the gate go red, and that record is inside the shared TTL. never bitten is its complement over the same denominator: those gates ran and were green, and nothing has ever shown them able to detect anything, so their green is a statement about this run and not about the gate. green at 0/0 is a separate and much weaker observation — the gate printed GREEN on a zero denominator, so its own tooth counter says it examined nothing. A gate can be green, non-zero, and still never bitten; that is the common case and it is now visible instead of implied.

partition: grounded + unsupported = 41 vs present 41 · named + unnamed + withheld = 22 vs open 22 · both reconcile

liar-kill conj=GPQN · all four conjuncts held

graded document: BUILDROOT tree, 31253 bytes · gates map: PRIMARY · stamped 4d 7h ago · source ../knowledge/status/evstamp_legalpractice.verdict

Gap class	What it is, and the work it names
NONE	No gap class fires on this board: every published claim is grounded, the declared gates ran and were green, no watch contract is unnamed or already landed, and the stamp is inside its TTL. That is a statement about evidence, not about depth, scale or polish.

This band reports the referee counts. The per-axis worklist rows — which axis is unsupported, which watch is ready to flip, which gap is unnamed — are printed by nx_swcompare_evidence legalpractice itself and are not carried on the stamp, so this page names the classes and the producer names the rows. That split is stated rather than hidden: a count without a worklist is not actionable, and this band is honest about which half of that it is.

Production map

Follow the dependencies, declared acceptance criteria and recorded priorities. Inspect source binding before treating a rank as executable work.

Ranking source binding: PLAN_MATRIX_BOUND_ONLY. Recorded priorities require current acceptance evidence and resource checks before execution.

Ranking matches the captured plan and matrix only. Latest execution outcome, research freshness, accepted delivery and investment return are unverified.

Recorded priority estimates

Order from nx_compare_rank (nx_dr_ocm: (deficit + cost-of-delay + option + enables) x sponsor x self-sufficiency x momentum / cost). FINISH rows are rungs whose symbol is present but whose organ is short of full adoption: listed before new work by this heuristic. Priority is not measured delivery cost or execution readiness. Stamp: # asof=1791487818 domain=legalpractice target_version=1.0 rungs=35 done=7 open=27 finish=1 ranker=nx_dr_ocm

#	Stage	Rung	Priority	Derivation
F	FINISH	Promote and register nx_mailmerge and nx_odt (source-only today) (LP2) mm_merge_one dossier	REGISTERED-DARK	callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)
#1	1.0	Client portal daemon promoted, realm-bound and served on the firm domain (LP9) lpd_serve_realm dossier	2000	v=15 m=2 c=15
#2	1.0	Signature, initial, date and text fields, per-signer secure links, signing UI (LP10) sf_place dossier	2000	v=20 m=2 c=20
#3	1.0	Tracked revisions and comments rendered in the browser view (LP11) dx_html_track dossier	1000	v=5 m=2 c=10
#4	1.0	Word MERGEFIELD field codes honoured (LP13) mm_mergefield dossier	1000	v=5 m=2 c=10
#5	1.0	Structure-preserving Word round-trip (LP12) dx_patch_para dossier	50	v=1 m=1 c=20
#6	later	Execution ladder keyed by instrument and Utah 2026 statute (LP23) lr_exec_ladder dossier	3000	v=15 m=3 c=15
#7	later	Every Utah execution element answered by the law engine (LP30) lr_exec_elements dossier	2000	v=15 m=2 c=15
#8	later	Sovereign PDF writer and PAdES-shaped signed PDF export (LP15) pdf_sign_pades dossier	1000	v=15 m=2 c=30
#9	later	Signer identity verification ladder (LP16) sc_signer_idv dossier	1000	v=20 m=1 c=20
#10	later	Passkey login with family-quorum and succession recovery in the portal daemon (LP28) pk_login dossier	1000	v=30 m=1 c=30
#11	later	One requirement set for a ceremony that touches several states (LP32) lr_exec_resolve dossier	1000	v=20 m=1 c=20
#12	later	Electronic-execution jurisdictions read into the registry from each state's own code (LP33) xl_wave_electronic dossier	1000	v=30 m=1 c=30
#13	later	Mobile-first signing and review surface measured against WCAG 2.2 AA (LP27) lpd_mobile_ceremony dossier	450	v=9 m=1 c=20
#14	later	Court forms refresh and staleness watch (LP20) forms_refresh dossier	400	v=2 m=2 c=10
#15	later	Contract review grounded on the clause library with cite-or-abstain (LP21) cl_review dossier	400	v=4 m=2 c=20
#16	later	Bulk send: merged documents become N envelopes (LP18) nx_env_bulk dossier	200	v=2 m=1 c=10
#17	later	Defined-terms and cross-reference consistency proofing (LP22) pf_defined_terms dossier	200	v=1 m=2 c=10
#18	later	Every document carries its instrument class (LP31) dg_instrument_class dossier	200	v=1 m=2 c=10
#19	later	Statutory forms per state in the template registry with a staleness watch (LP36) tmpl_state_forms dossier	200	v=2 m=2 c=20
#20	later	Certified paper copy of an electronic instrument (LP26) sc_paper_certify dossier	100	v=1 m=1 c=10
#21	later	A state's ceremony opens only on the acceptance of an attorney licensed there (LP35) lp_state_enable dossier	66	v=1 m=1 c=15
#22	later	Utah remote online notarization session record (LP17) ron_session dossier	50	v=1 m=1 c=20
#23	later	Remote witnessing session in electronic presence (LP24) sc_witness_session dossier	50	v=1 m=1 c=20
#24	later	Living estate vault with fiduciary release on a proven death event (LP29) lp_vault_release dossier	50	v=1 m=1 c=20
#25	later	Signer identity through Utah SEDI or an ISO mDL over the Digital Credentials API (LP25) sc_idv_sedi dossier	33	v=1 m=1 c=30
#26	later	Every remaining jurisdiction's paper execution law read into the registry (LP34) xl_wave_paper dossier	20	v=1 m=1 c=50
#27	later	Utah e-filing connector (LP19) efl_submit dossier	0	v=0 m=1 c=30

Declared roadmap — contract, acceptance, executor, effort

Rung	Closes with	Definition of done (pre-declared)	Executor	Est.
Import a Word, Google-exported or ODF document into the office as a versioned document (LP1)	of_import	POST /import accepts a .docx or .odt upload, extracts text via docx_read_text or odt_read_text into a spec that lands as v1, and keeps the ORIGINAL bytes beside it so /file returns the untouched original until the first edit; gate: upload then /file round-trips byte-identical, an oversize or non-package upload is refused with a reason	Organ	1 u
Promote and register nx_mailmerge and nx_odt (source-only today) (LP2)	mm_merge_one	/api/build, /api/promote and /api/tools/register for both organs; nx_mailmerge_gate 7 of 7 and nx_odt_gate re-run from the PROMOTED binaries, not from a scratch build; nx_catalog shows PROMOTED plus REGISTERED for both	Deploy	0.5 u
Firm office instance on the firm domain with the client realm (LP3) after LP1	od_session	nx_office_daemon accepts the andelinwest_docportal session as its handle and refuses unauthenticated saves; proxy row admin.andelinwest.com /office; documents owned by firm handles, ReBAC-gated; gate: unauthenticated GET of an owned document is refused, an authenticated save claims ownership; the shared open-mode office namespace is never exposed	Deploy	1 u
Sign a document version from the office (LP4) after LP1	of_sign_version	POST /sign runs nx_sign_ceremony over the version's CID with the consent gate and stores the certificate CID beside the version; gate: no-consent is refused, the certificate CID reproduces from the record, and the version's manifest row names the certificate	Organ	1 u

Milestones

Milestone	Rungs	Cumulative
L0 · Open, edit, merge and sign on the firm's host	LP1,LP2,LP3,LP4	3.5 u

Rung	Closes with	Definition of done (pre-declared)	Executor	Est.
Template registry: list, version and effective date (LP6) after LP2	dg_tmpl_list	Templates listed from the registry index with a version id and effective date per put; gate: two puts of one template id list as two versions with the newest current	Organ	0.5 u
Document lineage recorded at assembly time (LP7) after LP6	dg_assemble_lineage	dg_assemble writes a lineage record beside the document CID naming the template CID and every clause CID it merged; gate: the lineage of a re-assembled document is byte-identical to the first, and a document assembled after a clause revision names the new clause CID	Organ	0.5 u
Template and document staleness for the clerk desk (LP8) after LP7	dg_tmpl_stale	Given a clause revision, name every template that references it and every generated document whose lineage carries the old clause CID; gate plants one revision and asserts the exact stale set (templates and documents) plus a fresh control template that stays fresh; output is a worklist, never a count	Organ	2 u
Client portal daemon promoted, realm-bound and served on the firm domain (LP9) after LP4	lpd_serve_realm	nx_legal_portal_daemon promoted with file-backed per-tenant stores, bound to the andelinwest_docportal realm and proxied at portal.andelinwest.com with HTML views over lp_handle; gate: envelopes, status, checklist and document fetch answer over the edge, a cross-tenant document id is 404, a wet-signature Will is surfaced not offered	Deploy	1.5 u
Signature, initial, date and text fields, per-signer secure links, signing UI (LP10) after LP4	sf_place	Fields placed on the document through the annotation overlay (AN_SIGFIELD), each signer receives a single-use link bound to the envelope and routing order, and the signing page runs the consent ceremony; gate: a link used out of order is refused, a completed field set completes the envelope	Organ	2 u
Tracked revisions and comments rendered in the browser view (LP11) after LP1	dx_html_track	dx_to_html renders w:ins as insertions, w:del as strike-through and comments as anchored notes; gate: the docx_html gate gains three teeth (ins, del, comment) and a neg-control that a clean document renders none	Organ	1 u
Structure-preserving Word round-trip (LP12) after LP11	dx_patch_para	An edited paragraph is patched in place inside document.xml; every other byte of the package is identical; gate: nx_contentdiff over the two packages shows exactly the edited runs changed and Word opens the result	Organ	2 u
Word MERGEFIELD field codes honoured (LP13) after LP2	mm_mergefield	fldSimple and complex field runs resolved against the data table so a lawyer's existing Word merge template works unchanged; gate: a Word-authored template with split placeholder runs merges correctly	Organ	1 u
Co-editing wired into the office (LP14) after LP3,unidoc:UD8	of_coedit	nx_office_serve imports nx_coedit and two browsers converge on one document version; gate: the coedit live gate runs against the office route	Organ	1 u

Milestones

Milestone	Rungs	Cumulative
L1 · Client portal on the firm domain and the law-clerk desk	LP6,LP7,LP8,LP9,LP10,LP11,LP12,LP13,LP14	15 u

Rung	Closes with	Definition of done (pre-declared)	Executor	Est.
Sovereign PDF writer and PAdES-shaped signed PDF export (LP15) after LP4,unidoc:UD13	pdf_sign_pades	A PDF writer that emits the signed document with an embedded signature and validation data in the PAdES baseline shape over ISO 32000-2; gate: a third-party reader opens and validates the structure, a tampered byte fails validation	Organ	3 u
Signer identity verification ladder (LP16) after LP10	sc_signer_idv	Email OTP, then SMS, then knowledge-based, then government-ID document validation as declared levels recorded in the audit chain; gate: each level's evidence is present in the chain and a signature at a level below the envelope's requirement is refused	Organ	2 u
Utah remote online notarization session record (LP17) after LP16	ron_session	A record composing the notary's Utah location, the A/V session, the identification image reference and the recording reference per 46-1-3.6, sealed into the audit chain; gate: a session missing any statutory element is refused	Organ	2 u
Bulk send: merged documents become N envelopes (LP18) after LP13	nx_env_bulk	One action turns a mail-merge output set into N envelopes with per-recipient routing; gate: N documents give N envelopes and one refused document refuses only its own envelope	Organ	1 u
Utah e-filing connector (LP19)	efl_submit	Submission through the courts' eFiling API under the courts' non-disclosure agreement, composing efl_status_pure for filing-date and timeliness; gate: a rejected submission never reads as filed and a late one is named late	Organ	3 u
Court forms refresh and staleness watch (LP20) after LP8	forms_refresh	Utah courts forms re-fetched on a beat, hash-compared, each changed form named; gate: a planted change is named and an unchanged control is not	Organ	1 u
Contract review grounded on the clause library with cite-or-abstain (LP21) after LP8	cl_review	Every proposed edit is traceable to a governed clause or the reviewer abstains; gate: a review over a document with no matching clause abstains, and the Vals redlining protocol is re-run with our row published beside the lawyer baseline	Organ	2 u
Defined-terms and cross-reference consistency proofing (LP22) after LP11,unidoc:UD25	pf_defined_terms	Every capitalised defined term defined once and used consistently, every cross-reference resolves; gate: a planted undefined term and a dangling reference are named, clean prose yields none	Organ	1 u

Milestones

Milestone	Rungs	Cumulative
L2 · Beyond DocuSign for a Utah practice	LP15,LP16,LP17,LP18,LP19,LP20,LP21,LP22	30 u

Rung	Closes with	Definition of done (pre-declared)	Executor	Est.
Execution ladder keyed by instrument and Utah 2026 statute (LP23) after LP4,legal:LG4	lr_exec_ladder	nx_legal_regime grows a data table (knowledge/legal_exec_ladder.conf) naming per instrument type the statutory elements: an electronic will needs two witnesses in physical or electronic presence within a reasonable time (75-2-1405) and is self-proved by the testator's acknowledgment and the witnesses' affidavits before an authorized officer (75-2-1408); a trust, trust power, durable power of attorney, directive, guardian nomination or disclaimer takes an authorized officer's electronic signature for any required notarization (75-13-206) and electronic presence for any required witness (75-13-207); a deed or a vehicle title is refused; gate plants each instrument type and asserts the exact element set, a will without a scheduled second witness reads NEEDS-MORE never VALID, a deed reads REFUSED, and a control contract reads OK-UETA	Organ	1.5 u
Remote witnessing session in electronic presence (LP24) after LP23	sc_witness_session	A session record composing the signer, each witness, the real-time A/V reference, the ceremony head each witness attested and the time of each attestation, sealed into the audit chain; gate: an attestation without the session reference or outside the reasonable-time window is refused, two valid attestations complete the element, and a neg-control with one witness stays NEEDS-MORE	Organ	2 u
Signer identity through Utah SEDI or an ISO mDL over the Digital Credentials API (LP25) after LP16	sc_idv_sedi	The signing page requests only the attributes the ceremony needs through the browser credentials API, the sovereign verifier checks the presentation, and the audit chain records the verifier result and the attribute names, never the credential and never a card image; a digital guardian's presentation is accepted; gate: a presentation carrying an extra attribute is refused, a guardian presentation is accepted, and the recorded event contains no image bytes	Organ	3 u
Certified paper copy of an electronic instrument (LP26) after LP15	sc_paper_certify	A printable copy carrying the 75-13-209 affirmation text or the e-will officer certificate, the audit head and the certificate CID, produced from the record; gate: the copy reproduces byte-identically from the record and a tampered record changes the printed head	Organ	1 u
Mobile-first signing and review surface measured against WCAG 2.2 AA (LP27) after LP10	lpd_mobile_ceremony	The portal's signing page on a phone viewport: single column, 24 by 24 CSS pixel targets, no dragging, no redundant entry, the consent box and the sign action reachable in three taps from the link, measured by nx_uiq_atree and nx_uiq_perf on the served page; gate: the accessibility tree names every control, a 360 pixel viewport render has no horizontal scroll, and the ceremony completes over the edge from a phone user agent	Organ	2 u
Passkey login with family-quorum and succession recovery in the portal daemon (LP28) after LP9	pk_login	nx_legal_portal_daemon composes WebAuthn registration and assertion with sovereign verification of the authenticator signature, nx_sar_enroll_split and nx_sar_recover for K-of-N family recovery, nx_dm_heartbeat on every login and nx_succession_recover for the attested path; gate: a wrong assertion is refused, K-1 contacts cannot recover and K can, and a login inside the veto window cancels a pending succession	Organ	3 u
Living estate vault with fiduciary release on a proven death event (LP29) after LP28	lp_vault_release	The vault names the fiduciary roster per instrument and releases the trust instrument to the trustee and qualified beneficiaries and the will to the personal representative only on an attestation-gated event, each release a chained audit event; retention as DATA (the instrument for the life of the vault, a remote-notarization recording 10 years, trust records five years); gate: a release without attestation is refused, a release to a party off the roster is refused, and the audit chain names every release	Organ	2 u

Milestones

Milestone	Rungs	Cumulative
L3 · Mobile-first Utah estate portal under the 2026 statutes	LP23,LP24,LP25,LP26,LP27,LP28,LP29	44.5 u

Rung	Closes with	Definition of done (pre-declared)	Executor	Est.
Every Utah execution element answered by the law engine (LP30) after LP23,legal:LG4	lr_exec_elements	LP23 lands the three esign topic files; this rung adds the element topics LP23's done-rule names and the catalogue cannot yet type -- one typed topic per execution question (in which presence a witness must be, whether an authorized officer must notarize and by which means, whether and how the instrument is self-proved, what a remote notarization must record and retain, how a certified paper copy is made, how long each record is kept), each filled for US-UT from the enrolled bills and code sections already mirrored and pinned in legalpractice.refs with the deciding sentence quoted; lr_exec_elements(instrument, place, day) returns the whole element set by asking the engine, and nx_legal_compliance keeps no regime table of its own (the 2020 constants leave through the lifecycle with a mining receipt); gate: each Utah instrument class returns exactly its statutory element set with law ids and pins, a place with no rows returns the strictest set and never OK, a will reads NEEDS-MORE until every element is scheduled, and each quoted sentence verifies as an exact byte span of its mirror	Organ	1.5 u
Every document carries its instrument class (LP31) after LP7	dg_instrument_class	dg_assemble_lineage records the instrument class (will, codicil, revocable trust, trust power, durable power of attorney, health care directive, guardian nomination, disclaimer, deed, other) from the template that produced the document, an imported document takes a class only by an explicit recorded choice of a firm handle, and every consumer that asks about an unclassified document receives the strictest line (view only, no electronic ceremony offered); gate: an assembled will reads will, an import reads UNCLASSIFIED until classified and is refused a ceremony, and a reclassification is a new audit event that never rewrites the old one	Organ	1 u
One requirement set for a ceremony that touches several states (LP32) after LP30,legal:LG5	lr_exec_resolve	lr_exec_resolve(instrument, signer domicile, signer location, witness locations, notary state, day) composes the engine's several-places answer and returns one element set with every contributing law row named; with no sourced recognition row the set is the strictest over every place, so a ceremony is offered only when every place's law permits it; gate: a Utah signer with a witness located in a place whose rows are unread is refused by name, the same ceremony with every place sourced and permitting completes, and a planted recognition row relaxes exactly the element it names	Organ	2 u
Electronic-execution jurisdictions read into the registry from each state's own code (LP33) after LP30,legal:LG6	xl_wave_electronic	For every jurisdiction whose own statute authorizes an electronic will or an electronic non-testamentary instrument (the set is READ from each state's code, with the Uniform Law Commission enactment kit and one independent survey as second and third witnesses and every disagreement named), the whole topic family is sourced: one row per topic with the section number, the deciding sentence quoted from a pinned mirror of the state's own code, and effective and sunset dates (an enacted law not yet in force is a pending row); the coverage partition over the fifty-one codes is printed; gate holds every production row to its mirror by exact byte span, refuses a row whose mirror is a challenge page or a stub, and asserts the partition sums	Organ	3 u
Every remaining jurisdiction's paper execution law read into the registry (LP34) after LP33	xl_wave_paper	For every remaining jurisdiction the paper execution law of the same instrument classes is sourced the same way (witness count and qualification, notarization, self-proving affidavit, any other form of execution the state's statute recognizes), and each such place's electronic topics carry a row that names the wills act section read and records that it authorizes no electronic execution, so a refusal rests on a statute that was read rather than on one that was not; the page then tells a client in any state exactly what a valid ceremony needs and the portal never offers an electronic one where the law refuses; gate: coverage reads rowless 0 and unsourced 0 over the fifty-one codes for every topic of the family, and a planted unread state still answers the strictest line	Organ	5 u
A state's ceremony opens only on the acceptance of an attorney licensed there (LP35) after LP32	lp_state_enable	lp_state_enable reads, per jurisdiction and instrument class, an acceptance row of the accept plane made by an attorney licensed in that jurisdiction (the row names the bar number, the day and the law rows reviewed by id and pin) before the portal offers a ceremony there; sourced rows alone open the requirement view and never a ceremony; an acceptance is void once any reviewed row drifts or is superseded; gate: a sourced state with no acceptance shows its requirements and refuses the ceremony, an accepted state completes, and a drifted row closes the ceremony again until it is re-accepted	Organ	1.5 u
Statutory forms per state in the template registry with a staleness watch (LP36) after LP8,LP33	tmpl_state_forms	The template registry keys a template by jurisdiction and instrument class, the forms a state's statute prescribes (the self-proving affidavit, a statutory power of attorney, a directive form where the state provides one) are held as templates whose text is byte-compared with the pinned statute on a beat, and a changed statutory form names every template and every client document built from the old text; gate: a planted change to one state's form names exactly that state's templates and documents and a control state stays fresh	Organ	2 u

Milestones

Milestone	Rungs	Cumulative
L4 · Utah instruments decided by the one law engine and shown on the document page	LP30,LP31	47 u
L5 · Every state: execution law as sourced rows and a ceremony that is safe across state lines	LP32,LP33,LP34,LP35,LP36	60.5 u

Ladder to SOTA

Two dated targets, and every rung's role toward them. Best in class is the proven, deployed leader today; the frontier is the research edge as of its month. Each target is dated by a sotabar row and judged against the current month by the bar-age ruler (FRESH, ATTESTED with the fallback month named, or refused). Each rung is substrate (what the target's own methods consume), an arm (a sovereign arm that triangulates without competing for the number), a contender (its done-rule is a number against the target) or superseded (kept as capability, retired as a claim), and carries the rungs it stands on.

best-in-class (T-BIC-ESIGN), dated by SB-ESIGN = 2026-07 ATTESTED. DocuSign eSignature and Adobe Acrobat Sign: field placement, per-signer links, an identity-verification ladder, remote notarization through a partner network, mobile signing, bulk send and a vendor-held audit trail and certificate ref docusign-esign-oct

frontier (T-FRONTIER-ESIGN), dated by SB-ESIGN = 2026-07 ATTESTED. the instrument-keyed ceremony: execution elements decided by the one law engine per instrument and per state, witnesses in electronic presence and wallet identity over the Digital Credentials API, a hash-chained audit a third party verifies offline, the signature and integrity embedded in the delivered file (the SFDS direction) with PAdES LTA for PDF, and a certified paper copy that checks against the record ref arxiv-esign-oct

Rung	Role	Toward	Stands on	Why
LP1	substrate	T-BIC-ESIGN	-	the import every ceremony starts from
LP2	substrate	T-BIC-ESIGN	-	mail merge feeds templates and bulk send
LP3	substrate	T-BIC-ESIGN	LP1	the firm office daemon the ceremony is served from
LP4	contender	T-BIC-ESIGN	LP1	sign any version in place with a sealed certificate, measured against the rival ceremony
LP6	substrate	T-BIC-ESIGN	LP2	the template registry under document generation
LP7	substrate	T-FRONTIER-ESIGN	LP6	lineage carries the instrument class the ladder keys on
LP8	substrate	T-FRONTIER-ESIGN	LP7	the staleness worklist the statutory-form watch extends
LP9	arm	T-BIC-ESIGN	LP4	the client portal surface the ceremony is reached through
LP10	contender	T-BIC-ESIGN	LP4	field placement and per-signer links, where DocuSign and PandaDoc read Best
LP11	substrate	T-BIC-ESIGN	LP1	redline review without Word before signing
LP12	substrate	T-BIC-ESIGN	LP11	the in-place Word round trip keeps the signed file faithful
LP13	substrate	T-BIC-ESIGN	LP2	MERGEFIELD templates feed bulk send
LP14	superseded	T-BIC-ESIGN	LP3,unidoc:UD8 OPEN	retired as a claim onto unidoc:UD8 (ecosystem EC89, one capability is graded on one board): the office co-editing contract is unidoc's, LP14 is mapped on this board by reference to unidoc's of_coedit row and closes when UD8 closes; kept as the practice-side pointer, never climbed from here
LP15	contender	T-FRONTIER-ESIGN	LP4,unidoc:UD13 OPEN	PAdES LTA output is the embedded-signature leg
LP16	contender	T-BIC-ESIGN	LP10	the identity ladder measured against DocuSign Identify and NIST 800-63A-4
LP17	contender	T-BIC-ESIGN	LP16	the remote online notarization record under Utah 46-1-3.6
LP18	contender	T-BIC-ESIGN	LP13	bulk send measured against DocuSign and PandaDoc
LP19	arm	T-FRONTIER-ESIGN	-	e-filing hands the executed instrument to the court
LP20	arm	T-FRONTIER-ESIGN	LP8	the court-forms refresh feeds the statutory-form watch
LP21	arm	T-BIC-ESIGN	LP8	clause-grounded review before send
LP22	substrate	T-BIC-ESIGN	LP11,unidoc:UD25 DONE	defined-terms consistency before send
LP23	contender	T-FRONTIER-ESIGN	LP4,legal:LG4 DONE	the execution ladder keyed by instrument and statute, uncontested
LP24	contender	T-FRONTIER-ESIGN	LP23	electronic-presence witnessing sealed into the chain
LP25	contender	T-FRONTIER-ESIGN	LP16	wallet identity over the Digital Credentials API
LP26	contender	T-FRONTIER-ESIGN	LP15	the certified paper copy checked against the record
LP27	contender	T-BIC-ESIGN	LP10	the mobile ceremony measured by the WCAG 2.2 AA rulers
LP28	arm	T-FRONTIER-ESIGN	LP9	the passkey and succession login the vault release composes
LP29	arm	T-FRONTIER-ESIGN	LP28	the living estate vault released on a proven death event
LP30	substrate	T-FRONTIER-ESIGN	LP23,legal:LG4 DONE	the typed execution topics the ladder asks the engine for
LP31	substrate	T-FRONTIER-ESIGN	LP7	the instrument class the ladder keys on
LP32	contender	T-FRONTIER-ESIGN	LP30,legal:LG5 OPEN	one element set across states, uncontested
LP33	substrate	T-FRONTIER-ESIGN	LP30,legal:LG6 OPEN	electronic-execution rows for every authorizing state
LP34	substrate	T-FRONTIER-ESIGN	LP33	paper execution rows for every remaining state
LP35	arm	T-FRONTIER-ESIGN	LP32	a licensed attorney's acceptance opens a state's ceremony
LP36	substrate	T-FRONTIER-ESIGN	LP8,LP33	statutory forms per state under the staleness watch

Ladder verdict. LADDERED. Targets, rung roles and bars are counted in the tables below, each partition re-derived beside its total. Bars read FRESH against the current month 2026-10.

Ladder verdict, counted (17 rows, more than the 12-row disclosure bar)

Ladder verdict, counted
Class	Count	Note
targets	2	sotatarget rows on the plan
best in class	1	targets whose class is best-in-class, by code
frontier	1	targets whose class is frontier, by code
undated	0	targets naming no bar that exists
bad class	0	targets whose class is neither word
duplicate	0	target ids an earlier row already carries
rungs	35	rung rows on the plan
placed	35	rungs carrying a rungrole row
unplaced	0	rungs with no role toward any target
bad role	0	rungrole rows naming a role the ladder does not know
bad target	0	rungrole rows naming a target no sotatarget row declares
rungs, summed	35	RECONCILED: the parts sum to the total 35
substrate	15	what the target's own methods consume
arm	7	a sovereign arm that triangulates without competing for the number
contender	12	its done-rule is a number against the target
superseded	1	kept as capability, retired as a claim
placed, summed	35	RECONCILED: the parts sum to the total 35

Bar freshness, counted
Class	Count	Note
bars	1	sotabar rows on the plan
fresh	0	the bar month is the current month
attested	1	an older bar with a this-month barscan reporting no newer entry
stale	0	a this-month scan saw a newer month the bar ignores
unattested	0	nobody looked this month
malformed	0	a sotabar row missing a field
duplicate	0	bar ids an earlier row already carries
bars, summed	1	RECONCILED: the parts sum to the total 1
current month	2026-10	the month every bar is judged against

Treatment verdict. NOT DECLARED. No rung on this board declares its three-step treatment (a treat row naming the MCP row, the API route, the primitive it composes, the workflow that composes it and the agent beat that runs it); the ranker labels every rung TREATMENT-UNDECLARED until it does.

Inspect a rung and its prerequisites

Declared nodes 35. Rank input binding: PLAN_MATRIX_BOUND_ONLY. Dependency order is authored. Implementation, acceptance evidence, authority and resource readiness are unverified. No action is recommended or dispatched here.

Plan SHA-256 c801168a254a69a81bb7801191d2f4b3f3538245645a5098ec54eeb3048b93a1. Target rows 2; role rows 35. Existing risks and release worklog retain their own scope; no node completion is inferred.

Runtime observation coverage: 0 of 35 rungs have current, identity-bound execution observations. Observation may report RED. Accepted completion remains unknown; source presence, qualification and deployment do not establish it.

Use Enter or Space on a rung to inspect its contract. Prerequisite links locate another rung in this list; open its summary to inspect it. Estimates are authored effort, not forecasts.

LP1 — Import a Word, Google-exported or ODF document into the office as a versioned document
Prerequisites: None declared; this does not establish execution eligibility.
Contract: of_import
Acceptance: POST /import accepts a .docx or .odt upload, extracts text via docx_read_text or odt_read_text into a spec that lands as v1, and keeps the ORIGINAL bytes beside it so /file returns the untouched original until the first edit; gate: upload then /file round-trips byte-identical, an oversize or non-package upload is refused with a reason
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP2 — Promote and register nx_mailmerge and nx_odt (source-only today)
Prerequisites: None declared; this does not establish execution eligibility.
Contract: mm_merge_one
Acceptance: /api/build, /api/promote and /api/tools/register for both organs; nx_mailmerge_gate 7 of 7 and nx_odt_gate re-run from the PROMOTED binaries, not from a scratch build; nx_catalog shows PROMOTED plus REGISTERED for both
Authored effort: 0.5. Executor kind: Deploy. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP3 — Firm office instance on the firm domain with the client realm
Prerequisites: LP1 (acceptance unverified)
Contract: od_session
Acceptance: nx_office_daemon accepts the andelinwest_docportal session as its handle and refuses unauthenticated saves; proxy row admin.andelinwest.com /office; documents owned by firm handles, ReBAC-gated; gate: unauthenticated GET of an owned document is refused, an authenticated save claims ownership; the shared open-mode office namespace is never exposed
Authored effort: 1. Executor kind: Deploy. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP4 — Sign a document version from the office
Prerequisites: LP1 (acceptance unverified)
Contract: of_sign_version
Acceptance: POST /sign runs nx_sign_ceremony over the version's CID with the consent gate and stores the certificate CID beside the version; gate: no-consent is refused, the certificate CID reproduces from the record, and the version's manifest row names the certificate
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP6 — Template registry: list, version and effective date
Prerequisites: LP2 (acceptance unverified)
Contract: dg_tmpl_list
Acceptance: Templates listed from the registry index with a version id and effective date per put; gate: two puts of one template id list as two versions with the newest current
Authored effort: 0.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP7 — Document lineage recorded at assembly time
Prerequisites: LP6 (acceptance unverified)
Contract: dg_assemble_lineage
Acceptance: dg_assemble writes a lineage record beside the document CID naming the template CID and every clause CID it merged; gate: the lineage of a re-assembled document is byte-identical to the first, and a document assembled after a clause revision names the new clause CID
Authored effort: 0.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP8 — Template and document staleness for the clerk desk
Prerequisites: LP7 (acceptance unverified)
Contract: dg_tmpl_stale
Acceptance: Given a clause revision, name every template that references it and every generated document whose lineage carries the old clause CID; gate plants one revision and asserts the exact stale set (templates and documents) plus a fresh control template that stays fresh; output is a worklist, never a count
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP9 — Client portal daemon promoted, realm-bound and served on the firm domain
Prerequisites: LP4 (acceptance unverified)
Contract: lpd_serve_realm
Acceptance: nx_legal_portal_daemon promoted with file-backed per-tenant stores, bound to the andelinwest_docportal realm and proxied at portal.andelinwest.com with HTML views over lp_handle; gate: envelopes, status, checklist and document fetch answer over the edge, a cross-tenant document id is 404, a wet-signature Will is surfaced not offered
Authored effort: 1.5. Executor kind: Deploy. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP10 — Signature, initial, date and text fields, per-signer secure links, signing UI
Prerequisites: LP4 (acceptance unverified)
Contract: sf_place
Acceptance: Fields placed on the document through the annotation overlay (AN_SIGFIELD), each signer receives a single-use link bound to the envelope and routing order, and the signing page runs the consent ceremony; gate: a link used out of order is refused, a completed field set completes the envelope
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP11 — Tracked revisions and comments rendered in the browser view
Prerequisites: LP1 (acceptance unverified)
Contract: dx_html_track
Acceptance: dx_to_html renders w:ins as insertions, w:del as strike-through and comments as anchored notes; gate: the docx_html gate gains three teeth (ins, del, comment) and a neg-control that a clean document renders none
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP12 — Structure-preserving Word round-trip
Prerequisites: LP11 (acceptance unverified)
Contract: dx_patch_para
Acceptance: An edited paragraph is patched in place inside document.xml; every other byte of the package is identical; gate: nx_contentdiff over the two packages shows exactly the edited runs changed and Word opens the result
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP13 — Word MERGEFIELD field codes honoured
Prerequisites: LP2 (acceptance unverified)
Contract: mm_mergefield
Acceptance: fldSimple and complex field runs resolved against the data table so a lawyer's existing Word merge template works unchanged; gate: a Word-authored template with split placeholder runs merges correctly
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP14 — Co-editing wired into the office
Prerequisites: LP3 (acceptance unverified)
Contract: of_coedit
Acceptance: nx_office_serve imports nx_coedit and two browsers converge on one document version; gate: the coedit live gate runs against the office route
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP15 — Sovereign PDF writer and PAdES-shaped signed PDF export
Prerequisites: LP4 (acceptance unverified)
Contract: pdf_sign_pades
Acceptance: A PDF writer that emits the signed document with an embedded signature and validation data in the PAdES baseline shape over ISO 32000-2; gate: a third-party reader opens and validates the structure, a tampered byte fails validation
Authored effort: 3. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP16 — Signer identity verification ladder
Prerequisites: LP10 (acceptance unverified)
Contract: sc_signer_idv
Acceptance: Email OTP, then SMS, then knowledge-based, then government-ID document validation as declared levels recorded in the audit chain; gate: each level's evidence is present in the chain and a signature at a level below the envelope's requirement is refused
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP17 — Utah remote online notarization session record
Prerequisites: LP16 (acceptance unverified)
Contract: ron_session
Acceptance: A record composing the notary's Utah location, the A/V session, the identification image reference and the recording reference per 46-1-3.6, sealed into the audit chain; gate: a session missing any statutory element is refused
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP18 — Bulk send: merged documents become N envelopes
Prerequisites: LP13 (acceptance unverified)
Contract: nx_env_bulk
Acceptance: One action turns a mail-merge output set into N envelopes with per-recipient routing; gate: N documents give N envelopes and one refused document refuses only its own envelope
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP19 — Utah e-filing connector
Prerequisites: None declared; this does not establish execution eligibility.
Contract: efl_submit
Acceptance: Submission through the courts' eFiling API under the courts' non-disclosure agreement, composing efl_status_pure for filing-date and timeliness; gate: a rejected submission never reads as filed and a late one is named late
Authored effort: 3. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP20 — Court forms refresh and staleness watch
Prerequisites: LP8 (acceptance unverified)
Contract: forms_refresh
Acceptance: Utah courts forms re-fetched on a beat, hash-compared, each changed form named; gate: a planted change is named and an unchanged control is not
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP21 — Contract review grounded on the clause library with cite-or-abstain
Prerequisites: LP8 (acceptance unverified)
Contract: cl_review
Acceptance: Every proposed edit is traceable to a governed clause or the reviewer abstains; gate: a review over a document with no matching clause abstains, and the Vals redlining protocol is re-run with our row published beside the lawyer baseline
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP22 — Defined-terms and cross-reference consistency proofing
Prerequisites: LP11 (acceptance unverified)
Contract: pf_defined_terms
Acceptance: Every capitalised defined term defined once and used consistently, every cross-reference resolves; gate: a planted undefined term and a dangling reference are named, clean prose yields none
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP23 — Execution ladder keyed by instrument and Utah 2026 statute
Prerequisites: LP4 (acceptance unverified)
Contract: lr_exec_ladder
Acceptance: nx_legal_regime grows a data table (knowledge/legal_exec_ladder.conf) naming per instrument type the statutory elements: an electronic will needs two witnesses in physical or electronic presence within a reasonable time (75-2-1405) and is self-proved by the testator's acknowledgment and the witnesses' affidavits before an authorized officer (75-2-1408); a trust, trust power, durable power of attorney, directive, guardian nomination or disclaimer takes an authorized officer's electronic signature for any required notarization (75-13-206) and electronic presence for any required witness (75-13-207); a deed or a vehicle title is refused; gate plants each instrument type and asserts the exact element set, a will without a scheduled second witness reads NEEDS-MORE never VALID, a deed reads REFUSED, and a control contract reads OK-UETA
Authored effort: 1.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP24 — Remote witnessing session in electronic presence
Prerequisites: LP23 (acceptance unverified)
Contract: sc_witness_session
Acceptance: A session record composing the signer, each witness, the real-time A/V reference, the ceremony head each witness attested and the time of each attestation, sealed into the audit chain; gate: an attestation without the session reference or outside the reasonable-time window is refused, two valid attestations complete the element, and a neg-control with one witness stays NEEDS-MORE
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP25 — Signer identity through Utah SEDI or an ISO mDL over the Digital Credentials API
Prerequisites: LP16 (acceptance unverified)
Contract: sc_idv_sedi
Acceptance: The signing page requests only the attributes the ceremony needs through the browser credentials API, the sovereign verifier checks the presentation, and the audit chain records the verifier result and the attribute names, never the credential and never a card image; a digital guardian's presentation is accepted; gate: a presentation carrying an extra attribute is refused, a guardian presentation is accepted, and the recorded event contains no image bytes
Authored effort: 3. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP26 — Certified paper copy of an electronic instrument
Prerequisites: LP15 (acceptance unverified)
Contract: sc_paper_certify
Acceptance: A printable copy carrying the 75-13-209 affirmation text or the e-will officer certificate, the audit head and the certificate CID, produced from the record; gate: the copy reproduces byte-identically from the record and a tampered record changes the printed head
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP27 — Mobile-first signing and review surface measured against WCAG 2.2 AA
Prerequisites: LP10 (acceptance unverified)
Contract: lpd_mobile_ceremony
Acceptance: The portal's signing page on a phone viewport: single column, 24 by 24 CSS pixel targets, no dragging, no redundant entry, the consent box and the sign action reachable in three taps from the link, measured by nx_uiq_atree and nx_uiq_perf on the served page; gate: the accessibility tree names every control, a 360 pixel viewport render has no horizontal scroll, and the ceremony completes over the edge from a phone user agent
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP28 — Passkey login with family-quorum and succession recovery in the portal daemon
Prerequisites: LP9 (acceptance unverified)
Contract: pk_login
Acceptance: nx_legal_portal_daemon composes WebAuthn registration and assertion with sovereign verification of the authenticator signature, nx_sar_enroll_split and nx_sar_recover for K-of-N family recovery, nx_dm_heartbeat on every login and nx_succession_recover for the attested path; gate: a wrong assertion is refused, K-1 contacts cannot recover and K can, and a login inside the veto window cancels a pending succession
Authored effort: 3. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP29 — Living estate vault with fiduciary release on a proven death event
Prerequisites: LP28 (acceptance unverified)
Contract: lp_vault_release
Acceptance: The vault names the fiduciary roster per instrument and releases the trust instrument to the trustee and qualified beneficiaries and the will to the personal representative only on an attestation-gated event, each release a chained audit event; retention as DATA (the instrument for the life of the vault, a remote-notarization recording 10 years, trust records five years); gate: a release without attestation is refused, a release to a party off the roster is refused, and the audit chain names every release
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP30 — Every Utah execution element answered by the law engine
Prerequisites: LP23 (acceptance unverified)
Contract: lr_exec_elements
Acceptance: LP23 lands the three esign topic files; this rung adds the element topics LP23's done-rule names and the catalogue cannot yet type -- one typed topic per execution question (in which presence a witness must be, whether an authorized officer must notarize and by which means, whether and how the instrument is self-proved, what a remote notarization must record and retain, how a certified paper copy is made, how long each record is kept), each filled for US-UT from the enrolled bills and code sections already mirrored and pinned in legalpractice.refs with the deciding sentence quoted; lr_exec_elements(instrument, place, day) returns the whole element set by asking the engine, and nx_legal_compliance keeps no regime table of its own (the 2020 constants leave through the lifecycle with a mining receipt); gate: each Utah instrument class returns exactly its statutory element set with law ids and pins, a place with no rows returns the strictest set and never OK, a will reads NEEDS-MORE until every element is scheduled, and each quoted sentence verifies as an exact byte span of its mirror
Authored effort: 1.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP31 — Every document carries its instrument class
Prerequisites: LP7 (acceptance unverified)
Contract: dg_instrument_class
Acceptance: dg_assemble_lineage records the instrument class (will, codicil, revocable trust, trust power, durable power of attorney, health care directive, guardian nomination, disclaimer, deed, other) from the template that produced the document, an imported document takes a class only by an explicit recorded choice of a firm handle, and every consumer that asks about an unclassified document receives the strictest line (view only, no electronic ceremony offered); gate: an assembled will reads will, an import reads UNCLASSIFIED until classified and is refused a ceremony, and a reclassification is a new audit event that never rewrites the old one
Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP32 — One requirement set for a ceremony that touches several states
Prerequisites: LP30 (acceptance unverified)
Contract: lr_exec_resolve
Acceptance: lr_exec_resolve(instrument, signer domicile, signer location, witness locations, notary state, day) composes the engine's several-places answer and returns one element set with every contributing law row named; with no sourced recognition row the set is the strictest over every place, so a ceremony is offered only when every place's law permits it; gate: a Utah signer with a witness located in a place whose rows are unread is refused by name, the same ceremony with every place sourced and permitting completes, and a planted recognition row relaxes exactly the element it names
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP33 — Electronic-execution jurisdictions read into the registry from each state's own code
Prerequisites: LP30 (acceptance unverified)
Contract: xl_wave_electronic
Acceptance: For every jurisdiction whose own statute authorizes an electronic will or an electronic non-testamentary instrument (the set is READ from each state's code, with the Uniform Law Commission enactment kit and one independent survey as second and third witnesses and every disagreement named), the whole topic family is sourced: one row per topic with the section number, the deciding sentence quoted from a pinned mirror of the state's own code, and effective and sunset dates (an enacted law not yet in force is a pending row); the coverage partition over the fifty-one codes is printed; gate holds every production row to its mirror by exact byte span, refuses a row whose mirror is a challenge page or a stub, and asserts the partition sums
Authored effort: 3. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP34 — Every remaining jurisdiction's paper execution law read into the registry
Prerequisites: LP33 (acceptance unverified)
Contract: xl_wave_paper
Acceptance: For every remaining jurisdiction the paper execution law of the same instrument classes is sourced the same way (witness count and qualification, notarization, self-proving affidavit, any other form of execution the state's statute recognizes), and each such place's electronic topics carry a row that names the wills act section read and records that it authorizes no electronic execution, so a refusal rests on a statute that was read rather than on one that was not; the page then tells a client in any state exactly what a valid ceremony needs and the portal never offers an electronic one where the law refuses; gate: coverage reads rowless 0 and unsourced 0 over the fifty-one codes for every topic of the family, and a planted unread state still answers the strictest line
Authored effort: 5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP35 — A state's ceremony opens only on the acceptance of an attorney licensed there
Prerequisites: LP32 (acceptance unverified)
Contract: lp_state_enable
Acceptance: lp_state_enable reads, per jurisdiction and instrument class, an acceptance row of the accept plane made by an attorney licensed in that jurisdiction (the row names the bar number, the day and the law rows reviewed by id and pin) before the portal offers a ceremony there; sourced rows alone open the requirement view and never a ceremony; an acceptance is void once any reviewed row drifts or is superseded; gate: a sourced state with no acceptance shows its requirements and refuses the ceremony, an accepted state completes, and a drifted row closes the ceremony again until it is re-accepted
Authored effort: 1.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.
LP36 — Statutory forms per state in the template registry with a staleness watch
Prerequisites: LP8 (acceptance unverified), LP33 (acceptance unverified)
Contract: tmpl_state_forms
Acceptance: The template registry keys a template by jurisdiction and instrument class, the forms a state's statute prescribes (the self-proving affidavit, a statutory power of attorney, a directive form where the state provides one) are held as templates whose text is byte-compared with the pinned statute on a beat, and a changed statutory form names every template and every client document built from the old text; gate: a planted change to one state's form names exactly that state's templates and documents and a control state stays fresh
Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.
Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.

Learning and practice paths

No structured learning path is declared for this plan. Existing research, roadmap and worklog remain available above.

Rung dossiers — every record that bears on a rung, in one place

Joined by symbol, never typed. Each dossier is assembled on every publish from the rows this board already carries: the plan's rung row, the matrix row that carries its contract symbol (its status re-measured by the one symbol ruler), the gate the organ declares and the verdict the evidence referee recorded on its last run, the reference marks in the rung text, the design rows that name the rung and the work log filed against it. The capability matrix links each cell to its dossier and each dossier links back to its cell and forward to the rungs it stands on; a dependency naming no rung on this plan is written as UNRESOLVED rather than linked. Absences are named: NO-MATRIX-ROW, NO-GATE-DECLARED, UNRECORDED.

Gate verdicts: UNSTAMPED — no per-gate verdict artifact is published for this domain yet (nx_swcompare_evidence legalpractice writes it beside its stamp); every gate below reads UNRECORDED until it runs.

Gate declarations: knowledge/organ_gate.conf read from this working directory (1 rows) and from the estate root (196 rows); rows in both counted once: 0; declarations read: 197. Every declaration in either copy counts, so a stub beside the publisher can never hide the root.

LP1 Import a Word, Google-exported or ODF document into the office as a versioned document · cell NO-MATRIX-ROW · gate NO-MATRIX-ROW

Contract	`of_import` · executor Organ · 1 u · stands on nothing
Definition of done	POST /import accepts a .docx or .odt upload, extracts text via docx_read_text or odt_read_text into a spec that lands as v1, and keeps the ORIGINAL bytes beside it so /file returns the untouched original until the first edit; gate: upload then /file round-trips byte-identical, an oversize or non-package upload is refused with a reason
Matrix cell	NO-MATRIX-ROW — no matrix row carries `of_import`; the ranker reads this rung as unmapped and no cell can flip for it. Add the row and the join completes on the next publish.
Gate	the gate join needs a matrix row: no organ is named for this rung
Work log	2026-10-08 land 2026-10-07 the last two document rows that were graded here against the practice rivals, docx_read_text and docx_read_spec (every practice rival Yes, no discrimination on this board), moved home to /compare/unidoc and became @xrow references here (35971 to 35903 to the next receipt under CAS); of the nine document rows named on 2026-10-07, five are now references to unidoc or office (dx_to_html, odt_read_text, pf_to_html, of_save, nx_doc_serve_response earlier; docx_read_text, docx_read_spec now), three are @xrow office (dx_emit_track, dx_cm_add, pf_check), and the four watch rows that remain practice rows carry this board's own rungs: of_inline_runs and dx_patch_para (the beyond-Google-Docs round trip, LP12 class), dx_html_track (LP11, the read side of redlines for review without Word) and pf_defined_terms (LP22, the Litera class of proofing, practice-specific by nature). The first two are candidates to move home once unidoc declares the editor rungs; queued, not moved, because moving a watch row moves its rung and that is unidoc's RACI lane.

LP2 Promote and register nx_mailmerge and nx_odt (source-only today) · cell PRESENT · gate NO-GATE-DECLARED

Contract	`mm_merge_one` · executor Deploy · 0.5 u · stands on nothing
Definition of done	/api/build, /api/promote and /api/tools/register for both organs; nx_mailmerge_gate 7 of 7 and nx_odt_gate re-run from the PROMOTED binaries, not from a scratch build; nx_catalog shows PROMOTED plus REGISTERED for both
Matrix cell	ASSEMBLE: Mail merge -- one Word template times a data table gives N .docx files · `runtime/_hdl_build/nx_mailmerge.nx` · PRESENT decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_mailmerge`; declare `nx_mailmerge TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP3 Firm office instance on the firm domain with the client realm · cell PRESENT · gate NO-GATE-DECLARED

Contract	`od_session` · executor Deploy · 1 u · stands on LP1
Definition of done	nx_office_daemon accepts the andelinwest_docportal session as its handle and refuses unauthenticated saves; proxy row admin.andelinwest.com /office; documents owned by firm handles, ReBAC-gated; gate: unauthenticated GET of an owned document is refused, an authenticated save claims ownership; the shared open-mode office namespace is never exposed
Matrix cell	PORTAL: Firm office workspace mounted on the firm domain with the client realm · `runtime/_hdl_build/nx_office_daemon.nx` · PRESENT decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_office_daemon`; declare `nx_office_daemon TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP4 Sign a document version from the office · cell PRESENT · gate NO-GATE-DECLARED

Contract	`of_sign_version` · executor Organ · 1 u · stands on LP1
Definition of done	POST /sign runs nx_sign_ceremony over the version's CID with the consent gate and stores the certificate CID beside the version; gate: no-consent is refused, the certificate CID reproduces from the record, and the version's manifest row names the certificate
Matrix cell	SIGN: Sign any office document version in place -- consent-gated ceremony, per-version hash-chained log, sealed certificate served as the receipt · `runtime/nx_office_serve.nx` · PRESENT decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_office_serve`; declare `nx_office_serve TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP6 Template registry: list, version and effective date · cell PRESENT · gate NO-GATE-DECLARED

Contract	`dg_tmpl_list` · executor Organ · 0.5 u · stands on LP2
Definition of done	Templates listed from the registry index with a version id and effective date per put; gate: two puts of one template id list as two versions with the newest current
Matrix cell	ASSEMBLE: Template registry -- list, version and effective date as first-class data · `runtime/nx_tmplstale_lib.nx` · PRESENT decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_tmplstale_lib`; declare `nx_tmplstale_lib TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP7 Document lineage recorded at assembly time · cell PRESENT · gate NO-GATE-DECLARED

Contract	`dg_assemble_lineage` · executor Organ · 0.5 u · stands on LP6
Definition of done	dg_assemble writes a lineage record beside the document CID naming the template CID and every clause CID it merged; gate: the lineage of a re-assembled document is byte-identical to the first, and a document assembled after a clause revision names the new clause CID
Matrix cell	CLERK: Document lineage -- every generated document records the template CID and each clause CID it was built from · `runtime/nx_tmplstale_lib.nx` · PRESENT decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_tmplstale_lib`; declare `nx_tmplstale_lib TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP8 Template and document staleness for the clerk desk · cell PRESENT · gate NO-GATE-DECLARED

Contract	`dg_tmpl_stale` · executor Organ · 2 u · stands on LP7
Definition of done	Given a clause revision, name every template that references it and every generated document whose lineage carries the old clause CID; gate plants one revision and asserts the exact stale set (templates and documents) plus a fresh control template that stays fresh; output is a worklist, never a count
Matrix cell	CLERK: Template staleness -- a revised clause names every stale template and every client document built from the old text · `runtime/nx_tmplstale_lib.nx` · PRESENT decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_tmplstale_lib`; declare `nx_tmplstale_lib TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP9 Client portal daemon promoted, realm-bound and served on the firm domain · cell WATCHING · gate NO-GATE-DECLARED

Contract	`lpd_serve_realm` · executor Deploy · 1.5 u · stands on LP4
Definition of done	nx_legal_portal_daemon promoted with file-backed per-tenant stores, bound to the andelinwest_docportal realm and proxied at portal.andelinwest.com with HTML views over lp_handle; gate: envelopes, status, checklist and document fetch answer over the edge, a cross-tenant document id is 404, a wet-signature Will is surfaced not offered
Matrix cell	PORTAL: Client portal served on the firm domain with the docportal realm and HTML views · `runtime/_hdl_build/nx_legal_portal_daemon.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_legal_portal_daemon`; declare `nx_legal_portal_daemon TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	2026-09-03 measure nx_compare_rank legalpractice on 2026-09-03: rungs=21 done=7 open=14, target version 1.0, critical path LP11 (4800) then LP10 (1600) then LP13 (1600) then LP9 (800) then LP12 then LP14; LP2 reads FINISH REGISTERED-DARK (nx_mailmerge and nx_odt never invoked over MCP); LP14 read UNMAPPED because the co-editing matrix row carried cd_live_sync, corrected the same day to the _ABSENT_:of_coedit watch on nx_office_serve 2026-09-03 measure nx_catalog on 2026-09-03: nx_legal_portal_daemon BUILT and STAGED 143427 B, not promoted, not registered; nx_legal_portal, nx_legal_store, nx_doc_envelope, nx_doc_annotate, nx_doc_seal, nx_doc_serve and nx_legal_compliance are libs (adoption is importer count); nx_sign_ceremony and nx_sign_envelope REGISTERED-DARK; nx_office_daemon PROMOTED-UNREGISTERED which is correct for a daemon; nx_ron, nx_pdf_write and nx_forms_refresh absent exactly as their watch rows declare 2026-09-03 measure box at landing: load 18.87 against admission ceiling 40.00, D-state 7 (jbd2, nx_secret_scan, two nx_store_put, nx_web_shard_compact, nx_nav_sentinel, synostgd-disk), zombies 24; builds admissible by the ceiling, but sync MCP reads still 503 on the edge window (nx_catalog twice), so every census here ran through nx_job_run and read its artifact 2026-09-03 land Board landed and gated 2026-09-03: legalpractice.refs 19182 to 31437 B (15 rows, pins verified by nx_compare_refs_gate: mirrors-exist PASS, pins-match-filehash 1234 of 1234 PASS, declared-refs-cited-inline PASS; the one RED tooth left in the estate register is deploy.matrix key vercel-deploys, another lane's), legalpractice.matrix 24960 to 31253 B (63 rows, 7 new watch rows, the UNPINNED bars declared in the header), legalpractice.plan 14029 to 24883 B (L3, LP23 to LP29, 6 bars, 2 risks); nx_domain_admit legalpractice went REFUSE (no barcheck row and no UNPINNED declaration) to ADMIT with rows=63 grounded=41 absent=19 ungrounded=0; still owed there: C4 never-bitten nx_tmplstale_gate and nx_office_closed_gate, C5 second method class ABSENT 2026-09-03 queue Cross-board 2026-09-03: /compare/unidoc admitted the same day and its rung UD3 (dad_unidoc: GET /doc/<cid> served by the portal daemon through ud_render_path, POST annotate and sign composing nx_ann_add and of_sign_version) is the SAME daemon work as LP9 and the client-facing half of LP10 -- the unified page (nx_unidoc, promoted 50f18daf, gate 30 of 30) is the surface the firm's client sees a will or trust on, with the consent-gated sign form already emitted as a plain form; build UD3 once and both boards flip 2026-10-03 land the document viewer alpha is live on the firm's domain at https://andelinwest.com/alpha/docs/ (fictional samples only, noindex, registered as draft rows in the site's publish plane): the first client-visible proof of the native format and the unified page. The stage is ALPHA; beta needs the law panel (unidoc UD10) and the Utah execution rows (LP23, LP30) 2026-10-03 measure decision recorded with its evidence (which daemon carries the client document URL): the live vault daemon nx_docportal_admin_daemon already fronts andelinwest.com and serves /doc?cid= and /search, while nx_legal_portal_daemon is a loopback demo fixture around the lp_handle router. Recommendation: mount the document URL on the live daemon (unidoc UD3) and compose the legal portal routes as a library; do not deploy a second daemon. Still the operator's to confirm, together with delivery posture outside Utah, attorney sign-off per state (proposed yes) and opening portal.andelinwest.com 2026-10-03 measure the firm's whole domain was unreachable in a browser from 2026-09-30 22:59 UTC to 2026-10-03 about 22:28 UTC: its certificate had expired and nothing alarmed (deploy board DL22 and DL26 carry the mechanism and the fix). A portal that holds wills cannot ride an edge whose certificates lapse in silence; DL26 to DL31 are a dependency of any beta

LP10 Signature, initial, date and text fields, per-signer secure links, signing UI · cell WATCHING · gate NO-GATE-DECLARED

Contract	`sf_place` · executor Organ · 2 u · stands on LP4
Definition of done	Fields placed on the document through the annotation overlay (AN_SIGFIELD), each signer receives a single-use link bound to the envelope and routing order, and the signing page runs the consent ceremony; gate: a link used out of order is refused, a completed field set completes the envelope
Matrix cell	SIGN: Signature, initial, date and text fields placed on the document, per-signer secure links, signing UI · `runtime/nx_doc_annotate.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_doc_annotate`; declare `nx_doc_annotate TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	2026-10-07 queue rival census pass 1 on this board: adjudicate the proposals, refine the phrase table from the lesson rows and re-grade; the October 2026 DocuSign eSignature page carries no audit trail, identity verification, notary or eIDAS text (those live on the sibling pages mirrored in August), so column 1 cells for those rows are witnessed by the August mirrors until the sibling pages are re-read this month 2026-10-07 measure rival census (nx_rivalcensus, ecosystem EC88) on this board, 2026-10-07: pass 1 over the 12 mirrored practice pages read 52 keyed cells, 23 exact, 12 presence (Yes proposed where the seat graded Best), 17 disagree, 442 permil exact and 673 with presence; pass 2 after four phrases were replaced by the pages' own words (document generation, sets of documents, collect signatures, questionnaires) and two silent cells were withdrawn to No by evidence (ODT on all four rivals, PDF on NetDocuments) read 32 exact, 12 presence, 8 disagree, 615 permil exact and 846 with presence, ratchet HOLDS; the 8 remaining lessons in legalpractice.census_lessons are three phrase gaps (Word on the NetDocuments pages, bulk send on the PandaDoc pages, template on the NetDocuments automation page) and five Parts the seat holds against a vendor mention (eIDAS through partners, DocuSign Notary off Utah's vendor list, PandaDoc payments against billing from trust, Clio legal AI); 228 of 280 cells are UNKEYED and are the next phrase pass, from the pages' witnessed words only

LP11 Tracked revisions and comments rendered in the browser view · cell WATCHING · gate NO-GATE-DECLARED

Contract	`dx_html_track` · executor Organ · 1 u · stands on LP1
Definition of done	dx_to_html renders w:ins as insertions, w:del as strike-through and comments as anchored notes; gate: the docx_html gate gains three teeth (ins, del, comment) and a neg-control that a clean document renders none
Matrix cell	EDIT: Tracked revisions and comments rendered in the browser view · `runtime/_hdl_build/nx_docx.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_docx`; declare `nx_docx TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP12 Structure-preserving Word round-trip · cell WATCHING · gate NO-GATE-DECLARED

Contract	`dx_patch_para` · executor Organ · 2 u · stands on LP11
Definition of done	An edited paragraph is patched in place inside document.xml; every other byte of the package is identical; gate: nx_contentdiff over the two packages shows exactly the edited runs changed and Word opens the result
Matrix cell	EDIT: Structure-preserving Word round-trip -- edit one paragraph, every untouched XML byte identical · `runtime/_hdl_build/nx_docx.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_docx`; declare `nx_docx TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP13 Word MERGEFIELD field codes honoured · cell WATCHING · gate NO-GATE-DECLARED

Contract	`mm_mergefield` · executor Organ · 1 u · stands on LP2
Definition of done	fldSimple and complex field runs resolved against the data table so a lawyer's existing Word merge template works unchanged; gate: a Word-authored template with split placeholder runs merges correctly
Matrix cell	ASSEMBLE: Word MERGEFIELD field codes honoured, so a lawyer's existing merge template works unchanged · `runtime/_hdl_build/nx_mailmerge.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_mailmerge`; declare `nx_mailmerge TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP14 Co-editing wired into the office · cell NO-MATRIX-ROW · gate NO-MATRIX-ROW

Contract	`of_coedit` · executor Organ · 1 u · stands on LP3, unidoc:UD8 (UNRESOLVED: no such rung on this plan)
Definition of done	nx_office_serve imports nx_coedit and two browsers converge on one document version; gate: the coedit live gate runs against the office route
Matrix cell	NO-MATRIX-ROW — no matrix row carries `of_coedit`; the ranker reads this rung as unmapped and no cell can flip for it. Add the row and the join completes on the next publish.
Gate	the gate join needs a matrix row: no organ is named for this rung
Work log	2026-10-07 lesson OPERATOR 2026-10-07: the office rivals (Google Docs, Word, Acrobat, Nextcloud) belong to the document compare (unidoc) and this board is specific to the practice (DocuSign, Clio, NetDocuments, PandaDoc); measured the same hour: eleven rows here duplicate unidoc rows (dad_handle, dx_to_html, nx_ann_add, nx_doc_serve_response, nx_env_send, odt_read_text, of_coedit, of_import, of_save, of_sign_version, pf_to_html) graded against a different rival set, and LP14 is unidoc UD8 under another id; the fix is the cross-board row kind on ecosystem EC89 (a row rendered from its home board and graded once); until it lands LP14, LP15 and LP22 carry unidoc:UD8, unidoc:UD13 and unidoc:UD25 as deps so the ranker reads the home rung's state, and the eleven rows stay graded here only against the practice rivals' own pages 2026-10-08 land 2026-10-07 cross-board rows live (ecosystem EC89): five document rows that duplicated unidoc rows are now @xrow references to their home board (dx_to_html, odt_read_text, pf_to_html, of_save, nx_doc_serve_response), rendered on this page from unidoc's own cells under unidoc's columns and never re-graded here; the census partition reads xrows=5 and the position map, ranker and leaderboard count only this board's own rows; of_import (LP1), of_sign_version (LP4), of_coedit (LP14), dad_handle, nx_env_send and nx_ann_add stay as practice rows; the matrix landed on a predicted size ladder 36103 to 35762 to 35753 to 35758 to 35770 under CAS, every step byte-exact 2026-10-08 land 2026-10-07 second wave of cross-board references, chosen by the fleet duplicate census (nx_rivalcensus dupes, ecosystem EC89) rather than by hand: six more rows that graded a capability this board does not own became @xrow references to the home board that does: dx_emit_track, dx_cm_add, pf_check and of_llm_complete to /compare/office (the office suites are their rivals), dad_handle and the on-premise property row (its witness was docx_write, an office symbol) to /compare/unidoc; each reference keeps the practice reading in its note and names the practice-specific row that stays here (dx_html_track LP11, nx_ann_add, pf_defined_terms LP22, cl_review LP21, lp_handle and lpd_serve_realm LP9); landed on a predicted size ladder 35770 to 36036 in six steps, every receipt byte-exact; none of the six carried a rung, so the ranker stays at unmapped=0. Still duplicated and waiting on the ranker's reference-mapped rungs: of_import (LP1), of_sign_version (LP4) and of_coedit (LP14) against unidoc 2026-10-08 land 2026-10-07 the last two unidoc duplicates on this board became references once the ranker could carry a rung by reference (ecosystem EC89, nx_compare_rank 9caa9c3e): of_import (rung LP1, done) and of_coedit (rung LP14, open) are @xrow unidoc rows now, 36036 to 35913 to 35971 bytes under CAS; the ranker reads LP1 MAPPED-BY-REFERENCE state=DONE and LP14 MAPPED-BY-REFERENCE state=OPEN with unmapped=0 and xref_rows=13; LP14 is to be retired onto unidoc:UD8 through the lifecycle (UD8 already names the shared contract). This board now carries 13 references and grades 50 rows of its own; the fleet census reads no capability duplicated between legalpractice and unidoc 2026-10-08 retract 2026-10-07 LP14 RETIRED AS A CLAIM on this board (rungrole arm -> superseded, target T-BIC-ESIGN, successor unidoc:UD8): co-editing in the office is one capability and it is graded on /compare/unidoc (ecosystem EC89); this board keeps LP14 as the practice-side pointer, mapped by reference to unidoc's of_coedit row (the ranker reads RUNG LP14 MAPPED-BY-REFERENCE state=OPEN), and it closes the hour UD8 closes. Nothing is deleted: the rung row, its deps (LP3, unidoc:UD8) and every earlier log row stand; the ladder census now counts one superseded role here. The lifecycle (ecosystem EC71) owes the ranker a rung state that drops a superseded rung from the critical path instead of pricing it at its home deficit; until then LP14 ranks as its home row does, which is honest and visibly duplicated. 2026-10-08 measure 2026-10-07 the ranker candidate that carries the superseded rung state (ecosystem EC71, nx_compare_rank 29770f3d, shipping) read this board in the ship probe: RUNG LP14 SUPERSEDED target=T-BIC-ESIGN state=OPEN deps=LP3,unidoc:UD8, summary rungs=35 done=7 open=27 superseded=1 (the promoted ranker read open=28 and ranked LP14 number 3 of the 1.0 critical path with priority 1400 beside a DARK-CONTRACT note); the retired claim is no longer ranked, no longer the third PM filing (LP11 takes that seat), no longer a cross-board edge (XDEP edges 7 to 6, the unidoc:UD8-blocks-LP14 row gone), and is persisted as a superseded row in legalpractice.rank. The board's own work is unchanged: LP9, LP10 and LP11 lead the 1.0 critical path in both runs.

LP15 Sovereign PDF writer and PAdES-shaped signed PDF export · cell WATCHING · gate NO-GATE-DECLARED

Contract	`pdf_sign_pades` · executor Organ · 3 u · stands on LP4, unidoc:UD13 (UNRESOLVED: no such rung on this plan)
Definition of done	A PDF writer that emits the signed document with an embedded signature and validation data in the PAdES baseline shape over ISO 32000-2; gate: a third-party reader opens and validates the structure, a tampered byte fails validation
Matrix cell	SIGN: Signed PDF output with an embedded PAdES signature and long-term validation data · `runtime/nx_pdf_write.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_pdf_write`; declare `nx_pdf_write TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP16 Signer identity verification ladder · cell WATCHING · gate NO-GATE-DECLARED

Contract	`sc_signer_idv` · executor Organ · 2 u · stands on LP10
Definition of done	Email OTP, then SMS, then knowledge-based, then government-ID document validation as declared levels recorded in the audit chain; gate: each level's evidence is present in the chain and a signature at a level below the envelope's requirement is refused
Matrix cell	SIGN: Signer identity verification ladder -- email OTP, SMS, knowledge-based, government ID with document validation · `runtime/nx_sign_ceremony_lib.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_sign_ceremony_lib`; declare `nx_sign_ceremony_lib TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP17 Utah remote online notarization session record · cell WATCHING · gate NO-GATE-DECLARED

Contract	`ron_session` · executor Organ · 2 u · stands on LP16
Definition of done	A record composing the notary's Utah location, the A/V session, the identification image reference and the recording reference per 46-1-3.6, sealed into the audit chain; gate: a session missing any statutory element is refused
Matrix cell	SIGN: Remote online notarization -- Utah 46-1-3.6 session record with A/V recording and identity evidence · `runtime/nx_ron.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_ron`; declare `nx_ron TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP18 Bulk send: merged documents become N envelopes · cell WATCHING · gate NO-GATE-DECLARED

Contract	`nx_env_bulk` · executor Organ · 1 u · stands on LP13
Definition of done	One action turns a mail-merge output set into N envelopes with per-recipient routing; gate: N documents give N envelopes and one refused document refuses only its own envelope
Matrix cell	ASSEMBLE: Bulk send -- merged documents become N envelopes in one action · `runtime/nx_doc_envelope.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_doc_envelope`; declare `nx_doc_envelope TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP19 Utah e-filing connector · cell WATCHING · gate NO-GATE-DECLARED

Contract	`efl_submit` · executor Organ · 3 u · stands on nothing
Definition of done	Submission through the courts' eFiling API under the courts' non-disclosure agreement, composing efl_status_pure for filing-date and timeliness; gate: a rejected submission never reads as filed and a late one is named late
Matrix cell	SIGN: Utah e-filing connector -- submit through the courts' NDA-gated eFiling API · `runtime/nx_efile_lib.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_efile_lib`; declare `nx_efile_lib TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP20 Court forms refresh and staleness watch · cell WATCHING · gate NO-GATE-DECLARED

Contract	`forms_refresh` · executor Organ · 1 u · stands on LP8
Definition of done	Utah courts forms re-fetched on a beat, hash-compared, each changed form named; gate: a planted change is named and an unchanged control is not
Matrix cell	CLERK: Court forms refresh and staleness watch -- Utah forms re-fetched and hash-compared on a beat · `runtime/nx_forms_refresh.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_forms_refresh`; declare `nx_forms_refresh TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP21 Contract review grounded on the clause library with cite-or-abstain · cell WATCHING · gate NO-GATE-DECLARED

Contract	`cl_review` · executor Organ · 2 u · stands on LP8
Definition of done	Every proposed edit is traceable to a governed clause or the reviewer abstains; gate: a review over a document with no matching clause abstains, and the Vals redlining protocol is re-run with our row published beside the lawyer baseline
Matrix cell	AI: Contract review grounded on the clause library with cite-or-abstain · `runtime/nx_clause_lib.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_clause_lib`; declare `nx_clause_lib TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP22 Defined-terms and cross-reference consistency proofing · cell WATCHING · gate NO-GATE-DECLARED

Contract	`pf_defined_terms` · executor Organ · 1 u · stands on LP11, unidoc:UD25 (UNRESOLVED: no such rung on this plan)
Definition of done	Every capitalised defined term defined once and used consistently, every cross-reference resolves; gate: a planted undefined term and a dangling reference are named, clean prose yields none
Matrix cell	EDIT: Defined-terms and cross-reference consistency (the Litera class of proofing) · `runtime/_hdl_build/nx_proof.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_proof`; declare `nx_proof TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP23 Execution ladder keyed by instrument and Utah 2026 statute · cell WATCHING · gate NO-GATE-DECLARED

Contract	`lr_exec_ladder` · executor Organ · 1.5 u · stands on LP4, legal:LG4 (UNRESOLVED: no such rung on this plan)
Definition of done	nx_legal_regime grows a data table (knowledge/legal_exec_ladder.conf) naming per instrument type the statutory elements: an electronic will needs two witnesses in physical or electronic presence within a reasonable time (75-2-1405) and is self-proved by the testator's acknowledgment and the witnesses' affidavits before an authorized officer (75-2-1408); a trust, trust power, durable power of attorney, directive, guardian nomination or disclaimer takes an authorized officer's electronic signature for any required notarization (75-13-206) and electronic presence for any required witness (75-13-207); a deed or a vehicle title is refused; gate plants each instrument type and asserts the exact element set, a will without a scheduled second witness reads NEEDS-MORE never VALID, a deed reads REFUSED, and a control contract reads OK-UETA
Matrix cell	SIGN: Execution ladder keyed by instrument and Utah statute -- e-will under 75-2-1405 and 75-2-1408, trust or power of attorney or directive under 75-13-206 and 75-13-207, ESIGN 7003 carve-out otherwise · `runtime/nx_legal_compliance.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_legal_compliance`; declare `nx_legal_compliance TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	2026-09-03 lesson The execution ladder on this board was written against 2020 law: H.B. 181 (effective 2026-05-06) moved trusts, powers of attorney and directives out of the general UETA regime into a dedicated one with electronic presence for witnesses and an electronic-signature notarization, and S.B. 139 (same date) added secondary authentication to remote-notary identity and a 10-year recording retention; a ceremony keyed only to will-versus-not-will is a year behind the statute it enforces 2026-09-28 queue INTAKE 1790633100 routed by nx_intake_route (law-core-seat, epoch 1790633062) from operator: for the law domain are we making sure that these things are tightly coupled but that we can use them for import export etc so that we can have our compliance and ethics and legal and all that nailed d -- sponsor intake-1790633100 plus2 2026-09-28 queue HOW THE ONE LAW ENGINE SERVES LP23 (legal LG4 shipped 2026-09-28: nx_law_core law_ask over knowledge/law/, gate nx_law_core_gate 86/86, CLI nx_law on MCP): the execution ladder becomes rows of knowledge/law/esign.will.conf, esign.nontestamentary.conf and esign.deed.conf (topics already catalogued: electronic as the enum permitted, permitted-with-formalities, refused, and witnesses as an int, both max-direction, no world row), one row per jurisdiction and statute with its enrolled-bill mirror, pin and the deciding sentence quoted (Utah H.B. 181 UEEPDA for trusts, powers of attorney and directives from 2026-05-06; 75-2-1405 and 75-2-1408 for electronic wills), so nx_legal_compliance asks law_ask(esign.<class>, jurisdiction, day) instead of taking a caller flag over a 2020-law regime table; an unread jurisdiction reads the strictest line (refused, the most witnesses), never a clearance; the knowledge/legal_exec_ladder.conf this rung names is exactly those three files, so no second table is created. Recipe owner legalpractice LP23, engine owner legal LG4 (RACI law-core, legal A).

LP24 Remote witnessing session in electronic presence · cell WATCHING · gate NO-GATE-DECLARED

Contract	`sc_witness_session` · executor Organ · 2 u · stands on LP23
Definition of done	A session record composing the signer, each witness, the real-time A/V reference, the ceremony head each witness attested and the time of each attestation, sealed into the audit chain; gate: an attestation without the session reference or outside the reasonable-time window is refused, two valid attestations complete the element, and a neg-control with one witness stays NEEDS-MORE
Matrix cell	SIGN: Remote witnessing session -- electronic presence for the two witnesses of an e-will or the attesting individual of a non-testamentary document, with the real-time A/V record sealed into the audit chain · `runtime/nx_sign_ceremony_lib.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_sign_ceremony_lib`; declare `nx_sign_ceremony_lib TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP25 Signer identity through Utah SEDI or an ISO mDL over the Digital Credentials API · cell WATCHING · gate NO-GATE-DECLARED

Contract	`sc_idv_sedi` · executor Organ · 3 u · stands on LP16
Definition of done	The signing page requests only the attributes the ceremony needs through the browser credentials API, the sovereign verifier checks the presentation, and the audit chain records the verifier result and the attribute names, never the credential and never a card image; a digital guardian's presentation is accepted; gate: a presentation carrying an extra attribute is refused, a guardian presentation is accepted, and the recorded event contains no image bytes
Matrix cell	SIGN: Signer identity through Utah SEDI or an ISO mDL presented over the browser's Digital Credentials API -- selective disclosure, no card image stored · `runtime/nx_sign_ceremony_lib.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_sign_ceremony_lib`; declare `nx_sign_ceremony_lib TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	2026-09-03 measure September 2026 research banked as refs: Chrome 141 and Safari 26 ship the Digital Credentials API; Utah S.B. 275 creates the state-endorsed digital identity with a digital guardian and selective disclosure and repeals the electronic license certificate on 2027-01-01; NIST SP 800-63B-4 final since July 2025; the federal SECURE Notarization Act is still in committee; no rival page documents a wallet presentation, so LP25 is a lead nobody holds

LP26 Certified paper copy of an electronic instrument · cell WATCHING · gate NO-GATE-DECLARED

Contract	`sc_paper_certify` · executor Organ · 1 u · stands on LP15
Definition of done	A printable copy carrying the 75-13-209 affirmation text or the e-will officer certificate, the audit head and the certificate CID, produced from the record; gate: the copy reproduces byte-identically from the record and a tampered record changes the printed head
Matrix cell	SIGN: Certified paper copy of an electronic instrument -- the 75-13-209 affirmation for a trust or power of attorney and the e-will officer certificate, printed with the audit head and certificate CID · `runtime/nx_sign_ceremony_lib.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_sign_ceremony_lib`; declare `nx_sign_ceremony_lib TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP27 Mobile-first signing and review surface measured against WCAG 2.2 AA · cell WATCHING · gate NO-GATE-DECLARED

Contract	`lpd_mobile_ceremony` · executor Organ · 2 u · stands on LP10
Definition of done	The portal's signing page on a phone viewport: single column, 24 by 24 CSS pixel targets, no dragging, no redundant entry, the consent box and the sign action reachable in three taps from the link, measured by nx_uiq_atree and nx_uiq_perf on the served page; gate: the accessibility tree names every control, a 360 pixel viewport render has no horizontal scroll, and the ceremony completes over the edge from a phone user agent
Matrix cell	PORTAL: Mobile-first signing and review surface -- one-thumb ceremony, WCAG 2.2 AA target size and accessible authentication, no app install, on the phone the client already holds · `runtime/_hdl_build/nx_legal_portal_daemon.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_legal_portal_daemon`; declare `nx_legal_portal_daemon TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	2026-09-03 queue Build order for the doc-portal lane now that the board carries L3: LP10 signing UI (fields, per-signer links) and LP27 the mobile ceremony on the same page, then LP9 promote the portal daemon with file-backed stores behind portal.andelinwest.com (opening a public surface is the operator's call), then LP28 passkey and recovery, then LP23 and LP24 for e-wills, then LP25 SEDI; LP11 and LP13 stay on the office lane; the foundational byte-up work (PDF writer LP15, e-filing LP19) is the other lane's

LP28 Passkey login with family-quorum and succession recovery in the portal daemon · cell WATCHING · gate NO-GATE-DECLARED

Contract	`pk_login` · executor Organ · 3 u · stands on LP9
Definition of done	nx_legal_portal_daemon composes WebAuthn registration and assertion with sovereign verification of the authenticator signature, nx_sar_enroll_split and nx_sar_recover for K-of-N family recovery, nx_dm_heartbeat on every login and nx_succession_recover for the attested path; gate: a wrong assertion is refused, K-1 contacts cannot recover and K can, and a login inside the veto window cancels a pending succession
Matrix cell	PORTAL: Passkey login with family-quorum and succession recovery -- device biometric, K-of-N trusted contacts, attestation-gated succession and a proof-of-life veto window · `runtime/_hdl_build/nx_social_auth_recover.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_social_auth_recover`; declare `nx_social_auth_recover TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	2026-09-25 queue PM seat: authz AZ9 wauth_assert_verify (declared this hour from operator goal child R10 1790355010) is the estate-wide WebAuthn Level 3 verifier on the family realm, so LP28 should compose it for the portal passkey login rather than build a second authenticator-signature verifier inside nx_legal_portal_daemon; the family-quorum and succession recovery (nx_sar_enroll_split, nx_sar_recover, nx_succession_recover) stay LP28 own

LP29 Living estate vault with fiduciary release on a proven death event · cell WATCHING · gate NO-GATE-DECLARED

Contract	`lp_vault_release` · executor Organ · 2 u · stands on LP28
Definition of done	The vault names the fiduciary roster per instrument and releases the trust instrument to the trustee and qualified beneficiaries and the will to the personal representative only on an attestation-gated event, each release a chained audit event; retention as DATA (the instrument for the life of the vault, a remote-notarization recording 10 years, trust records five years); gate: a release without attestation is refused, a release to a party off the roster is refused, and the audit chain names every release
Matrix cell	PORTAL: Living estate vault -- the client's signed instruments, the fiduciary roster and a release rule that hands the right documents to the trustee, personal representative or beneficiaries on a proven death event · `runtime/nx_legal_portal.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_legal_portal`; declare `nx_legal_portal TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP30 Every Utah execution element answered by the law engine · cell WATCHING · gate UNRECORDED

Contract	`lr_exec_elements` · executor Organ · 1.5 u · stands on LP23, legal:LG4 (UNRESOLVED: no such rung on this plan)
Definition of done	LP23 lands the three esign topic files; this rung adds the element topics LP23's done-rule names and the catalogue cannot yet type -- one typed topic per execution question (in which presence a witness must be, whether an authorized officer must notarize and by which means, whether and how the instrument is self-proved, what a remote notarization must record and retain, how a certified paper copy is made, how long each record is kept), each filled for US-UT from the enrolled bills and code sections already mirrored and pinned in legalpractice.refs with the deciding sentence quoted; lr_exec_elements(instrument, place, day) returns the whole element set by asking the engine, and nx_legal_compliance keeps no regime table of its own (the 2020 constants leave through the lifecycle with a mining receipt); gate: each Utah instrument class returns exactly its statutory element set with law ids and pins, a place with no rows returns the strictest set and never OK, a will reads NEEDS-MORE until every element is scheduled, and each quoted sentence verifies as an exact byte span of its mirror
Matrix cell	SIGN: Every Utah execution element answered by the law engine -- witness presence, notarization means, self-proving, the remote-notarization record and its retention, the certified paper copy and record retention, each a typed topic filled from the enrolled bills · `runtime/nx_law_core.nx` · WATCHING decl
Gate	`nx_law_core_gate` · UNRECORDED — no recorded verdict for this gate (it is declared for the organ but the evidence referee's last run did not record it: it is not on this board's gates map, or the referee has not run since the per-gate record shipped)
Work log	2026-10-03 measure 2026-10-03 opening measurement for the Utah-then-every-state program: nx_compare_rank legalpractice rungs=28 done=7 open=21, target version 1.0, critical path LP9 then LP10 then LP11 then LP13 then LP14 then LP12, LP23 seventh with sponsor plus2; nx_barfresh NO-BAR, nx_ladder NO-LADDER (28 rungs unplaced), treatment undeclared, XDEP edges=0; nx_catalog: nx_legal_portal_daemon still BUILT and STAGED 143427 B and unpromoted (the stage is a month old), nx_docportal_admin_daemon LIVE 1744488 B, nx_doc_view REGISTERED with no cap minted, nx_sign_ceremony, nx_sign_envelope, nx_legal_svc and nx_docgen REGISTERED-DARK, nx_law_core and nx_legal_compliance libs; knowledge/law lists 16 files (trade topics, topics.conf, jurisdictions.conf) and no esign file, so every execution topic refuses no-table for every place; nx_compare_rank unidoc rungs=9 done=1, UD3 the portal route still open and UD2 and UD9 unmapped 2026-10-03 queue Build order for the program (the ranker decides within it): (1) LP23 the three esign files with US-UT rows from the pinned mirrors, then LP30 the element topics and lr_exec_elements; (2) unidoc UD3 the portal route and unidoc UD10 the requirements panel, so the page a client opens states what the instrument needs and under which section, with LP31 the instrument class so the panel knows what it is looking at; (3) legal LG6 coverage and LG5 the several-places answer, then LP32; (4) LP33 the electronic-execution jurisdictions, LP34 every remaining jurisdiction, LP36 the statutory forms, with legal LG7 the drift watch running before the second state lands; LP35 opens a state's ceremony only on an attorney's acceptance. Owed before any of it is called SOTA: this board's dated bars and ladder (three independent current witnesses per bar: the state codes and uniform acts as the standard, a standards source for identity and signature format, and the rivals' current product pages labelled vendor claims), and the October attestation of the legal board's bar. The estimates for LP33 and LP34 are provisional: the cost per jurisdiction is measured on Utah first and the two figures are re-derived from it 2026-10-03 retract The seven watch rows for LP30 to LP36 were appended to legalpractice.matrix with all four rival cells unassessed (code 4) and withdrawn within the hour: the emitter rightly refuses to draw a position map while any peer cell is unassessed, so the page published at 1791044729 read Position map unassessed, 28 peer cells, where the page before it carried the map. The matrix is back to its 31253 bytes and the rungs stay on this plan, reading UNMAPPED until each row returns with its rival cells assessed from cited pages. Lesson: a watch row costs the page its comparative figure unless its rival cells are assessed, so the rival read comes before the row, in the same leg as the bars 2026-10-07 land 2026-10-07 board hygiene: seven rungs (LP30 to LP36) had no matrix row and nx_compare_rank read them UNMAPPED; watch rows landed on legalpractice.matrix hosted on runtime/nx_law_core.nx (LP30, LP32, LP33, LP34), runtime/nx_tmplstale_lib.nx (LP31, LP36) and runtime/nx_legal_portal.nx (LP35), the dated bar SB-ESIGN (July 2026, attested by a 2026-10-07 read of the listing) with two targets and a role on every rung make the board LADDERED, and the rival census (ecosystem EC88) gets legalpractice.rivals (12 mirrored pages over four columns) and legalpractice.cellkeys (46 keyed cells from the pages' witnessed words)

LP31 Every document carries its instrument class · cell WATCHING · gate NO-GATE-DECLARED

Contract	`dg_instrument_class` · executor Organ · 1 u · stands on LP7
Definition of done	dg_assemble_lineage records the instrument class (will, codicil, revocable trust, trust power, durable power of attorney, health care directive, guardian nomination, disclaimer, deed, other) from the template that produced the document, an imported document takes a class only by an explicit recorded choice of a firm handle, and every consumer that asks about an unclassified document receives the strictest line (view only, no electronic ceremony offered); gate: an assembled will reads will, an import reads UNCLASSIFIED until classified and is refused a ceremony, and a reclassification is a new audit event that never rewrites the old one
Matrix cell	ASSEMBLE: Every document carries its instrument class -- will, codicil, trust, trust power, durable power of attorney, directive, guardian nomination, disclaimer, deed or other, recorded from the template that produced it · `runtime/nx_tmplstale_lib.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_tmplstale_lib`; declare `nx_tmplstale_lib TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

LP32 One requirement set for a ceremony that touches several states · cell WATCHING · gate UNRECORDED

Contract	`lr_exec_resolve` · executor Organ · 2 u · stands on LP30, legal:LG5 (UNRESOLVED: no such rung on this plan)
Definition of done	lr_exec_resolve(instrument, signer domicile, signer location, witness locations, notary state, day) composes the engine's several-places answer and returns one element set with every contributing law row named; with no sourced recognition row the set is the strictest over every place, so a ceremony is offered only when every place's law permits it; gate: a Utah signer with a witness located in a place whose rows are unread is refused by name, the same ceremony with every place sourced and permitting completes, and a planted recognition row relaxes exactly the element it names
Matrix cell	SIGN: One requirement set for a ceremony that touches several states -- the strictest sourced line over the signer's domicile, the signer's location, each witness's place and the notary's commissioning state · `runtime/nx_law_core.nx` · WATCHING decl
Gate	`nx_law_core_gate` · UNRECORDED — no recorded verdict for this gate (it is declared for the organ but the evidence referee's last run did not record it: it is not on this board's gates map, or the referee has not run since the per-gate record shipped)
Work log	no log row names this rung yet

LP33 Electronic-execution jurisdictions read into the registry from each state's own code · cell WATCHING · gate UNRECORDED

Contract	`xl_wave_electronic` · executor Organ · 3 u · stands on LP30, legal:LG6 (UNRESOLVED: no such rung on this plan)
Definition of done	For every jurisdiction whose own statute authorizes an electronic will or an electronic non-testamentary instrument (the set is READ from each state's code, with the Uniform Law Commission enactment kit and one independent survey as second and third witnesses and every disagreement named), the whole topic family is sourced: one row per topic with the section number, the deciding sentence quoted from a pinned mirror of the state's own code, and effective and sunset dates (an enacted law not yet in force is a pending row); the coverage partition over the fifty-one codes is printed; gate holds every production row to its mirror by exact byte span, refuses a row whose mirror is a challenge page or a stub, and asserts the partition sums
Matrix cell	CLERK: Electronic-execution jurisdictions read into the registry from each state's own code -- one row per topic with the section, the quoted deciding sentence, effective and sunset dates · `runtime/nx_law_core.nx` · WATCHING decl
Gate	`nx_law_core_gate` · UNRECORDED — no recorded verdict for this gate (it is declared for the organ but the evidence referee's last run did not record it: it is not on this board's gates map, or the referee has not run since the per-gate record shipped)
Work log	2026-10-03 measure Researcher reach for the state census, measured 2026-10-03: nx_research_fetch read the Uniform Law Commission Electronic Wills Act page (status 200, 107722 B, mirror knowledge/fetched/rf_6f764188.raw, sha256 41308e392c05836a24502965e4d91bf002af7dd6a3304a4dc775d34079fb1bdf) and the mirror carries the enactment kit and final act links but NO enactment list: the map is a Power BI frame the fetcher cannot read (the string Utah occurs 0 times in the body). So the census of which states enacted what is read from each state's own code, with the enactment kit document as a second witness; secondary web pages read the same day disagree with one another on which states adopted the uniform text, which is the reason no state list is written on this board before it is read from primary sources

LP34 Every remaining jurisdiction's paper execution law read into the registry · cell WATCHING · gate UNRECORDED

Contract	`xl_wave_paper` · executor Organ · 5 u · stands on LP33
Definition of done	For every remaining jurisdiction the paper execution law of the same instrument classes is sourced the same way (witness count and qualification, notarization, self-proving affidavit, any other form of execution the state's statute recognizes), and each such place's electronic topics carry a row that names the wills act section read and records that it authorizes no electronic execution, so a refusal rests on a statute that was read rather than on one that was not; the page then tells a client in any state exactly what a valid ceremony needs and the portal never offers an electronic one where the law refuses; gate: coverage reads rowless 0 and unsourced 0 over the fifty-one codes for every topic of the family, and a planted unread state still answers the strictest line
Matrix cell	CLERK: Every remaining jurisdiction's paper execution law read into the registry -- witness count and qualification, notarization, the self-proving affidavit and every other recognized form · `runtime/nx_law_core.nx` · WATCHING decl
Gate	`nx_law_core_gate` · UNRECORDED — no recorded verdict for this gate (it is declared for the organ but the evidence referee's last run did not record it: it is not on this board's gates map, or the referee has not run since the per-gate record shipped)
Work log	no log row names this rung yet

LP35 A state's ceremony opens only on the acceptance of an attorney licensed there · cell WATCHING · gate NO-GATE-DECLARED

Contract	`lp_state_enable` · executor Organ · 1.5 u · stands on LP32
Definition of done	lp_state_enable reads, per jurisdiction and instrument class, an acceptance row of the accept plane made by an attorney licensed in that jurisdiction (the row names the bar number, the day and the law rows reviewed by id and pin) before the portal offers a ceremony there; sourced rows alone open the requirement view and never a ceremony; an acceptance is void once any reviewed row drifts or is superseded; gate: a sourced state with no acceptance shows its requirements and refuses the ceremony, an accepted state completes, and a drifted row closes the ceremony again until it is re-accepted
Matrix cell	PORTAL: A state's ceremony opens only on the acceptance of an attorney licensed there -- an accept-plane row naming the bar number, the day and the law rows reviewed by id and pin · `runtime/nx_legal_portal.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_legal_portal`; declare `nx_legal_portal TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	2026-10-03 queue OPERATOR DECISIONS this program waits on, none of which blocks the Utah stage: (a) the delivery posture outside Utah -- the firm's own practice where its lawyers are admitted, or a platform an attorney licensed in each state operates; the law engine answers execution law either way, and the posture becomes its own sourced topic before any non-Utah ceremony opens; (b) whether a state's ceremony requires the LP35 acceptance by an attorney licensed there (proposed: yes, with sourced rows alone opening the requirement view only); (c) which daemon carries the client's document URL -- the live vault daemon (unidoc UD3) or the staged legal portal daemon (LP9) -- to be settled by reading both sources before either is deployed, since two portals for one client is the duplicate this board exists to prevent; (d) opening portal.andelinwest.com stays the operator's call as recorded on 2026-09-03

LP36 Statutory forms per state in the template registry with a staleness watch · cell WATCHING · gate NO-GATE-DECLARED

Contract	`tmpl_state_forms` · executor Organ · 2 u · stands on LP8, LP33
Definition of done	The template registry keys a template by jurisdiction and instrument class, the forms a state's statute prescribes (the self-proving affidavit, a statutory power of attorney, a directive form where the state provides one) are held as templates whose text is byte-compared with the pinned statute on a beat, and a changed statutory form names every template and every client document built from the old text; gate: a planted change to one state's form names exactly that state's templates and documents and a control state stays fresh
Matrix cell	CLERK: Statutory forms per state in the template registry with a staleness watch -- the self-proving affidavit, a statutory power of attorney and a directive form, byte-compared with the pinned statute on a beat · `runtime/nx_tmplstale_lib.nx` · WATCHING decl
Gate	NO-GATE-DECLARED — `knowledge/organ_gate.conf` carries no row for `nx_tmplstale_lib`; declare `nx_tmplstale_lib TAB <gate>` and the ship loop proves it and the verdict lands here.
Work log	no log row names this rung yet

dossiers=35 cells_joined=33 no_matrix_row=2 (sum 35) gates_recorded=0 gates_unrecorded=4 no_gate_declared=29 (sum 33 of cells_joined) evgates=UNSTAMPED

Capability comparisons

Compare the field, search individual capabilities and open their source and adoption evidence. Documented presence does not establish comparative quality.

Position map — centrality and distinctiveness

The four-quadrant map the field uses for brand strategy (Dawar and Bagga, HBR June 2015), re-derived from this matrix on every publish. Centrality is the share of the category's feature mass a player covers, each feature weighted by how many hold it; distinctiveness is the average lead over each rival on the rows the player holds; breadth is the depth-weighted share of the whole matrix (the bubble); depth is how deeply the rows held are held; momentum is the day-over-day move off the spine (green rising, red falling, grey until day two); the dashed path runs first day → previous day → today. Dividers are the category means. Axes are fitted to the field of play, so read the tick numerals, not the frame. Rival marks are documented presence, so a rival's position reads the record, never its quality. The picture grades its own readability below; the table beside it is the same data for a screen reader or a second method.

Rows. 41 feature rows mapped of 55 matrix rows; 14 substrate rows (kernels, bounds and instruments the plan's rungrole marks substrate) are the estate's scaffolding, not category features, and stay off the map

Views. 2D cut: centrality, distinctiveness · 3D cube: centrality, distinctiveness, breadth · axes registered: centrality, distinctiveness, breadth, depth, momentum · a board picks its own in knowledge/compare/legalpractice.cdmap (cut|x|y, cube|x|y|z); absent = the HBR defaults

bubble area = breadth · ring = momentum (green rising, red falling, grey until day two) · dashed = category means · axes fitted to the field of play: centrality 650–950, distinctiveness 0–500 of 0–1000 permil (the full range put every player in one corner)
readability of the 2D cut, self-graded by the layout ruler: label overlaps 0 · labels over marks 0 · off-canvas 0 · unresolved labels 0 · mark overlaps 0 (a fact of the data: two players that close are that close) · data spread 616 permil of the plot · quadrant words unseated 0
text contrast, measured with wcag2-ratio (floors from contrast.conf), light theme: labels 16.24 (floor 4.50) · notes 16.24 (floor 4.50) · quadrant words 5.89 (floor 4.50) · tick numerals 5.89 (floor 4.50) · axis titles 5.59 (floor 4.50) · dark theme: labels 13.78 (floor 4.50) · quadrant words 5.55 (floor 4.50) · axis titles 5.97 (floor 4.50) · dark classes under their floor 0 (one figure serves both themes: a dark shortfall is a token to fix, never a class to hide) · classes refused under their floor 0 (a refused class is not drawn; the scale classes are measured, never hidden) · export: SVG PNG (receipt, rendered by the estate's own rasteriser from this page)

axes fitted: centrality 650–950 · distinctiveness 0–500 · breadth 200–550 permil · farther bubbles are painted first, nearer ones over them · the floor shadow is each bubble's (x, y) at height 0
readability of the 3D cube, self-graded by the layout ruler: label overlaps 0 · labels over marks 0 · off-canvas 0 · unresolved labels 0 · mark overlaps 1 (a fact of the data: two players that close are that close) · data spread 315 permil of the plot

Nishi DocuSign Clio NetDocuments PandaDoc
10 panels over 5 registered axes, every pair once (the lower axis on x, the higher on y) · each panel fitted to its own field of play, first and last tick numerals shown · no labels in a small cut, the legend names the colours; the grade below reports the mark terms only (MM summed over the panels, spread averaged)
readability of the small multiples, self-graded by the layout ruler: label overlaps 0 · labels over marks 0 · off-canvas 0 · unresolved labels 0 · mark overlaps 1 (a fact of the data: two players that close are that close) · data spread 651 permil of the plot

Player	Quadrant	centrality	distinctiveness	breadth	depth	momentum	Rows held	Days on spine	First seen
Nishi	Unconventional	680	390	414	772	-16 since 2026-10-07	22	13	2026-09-15
DocuSign	Mainstream	823	215	390	666	+51 since 2026-10-07	24	13	2026-09-15
Clio	Aspirational	873	261	447	654	+47 since 2026-10-07	28	13	2026-09-15
NetDocuments	Peripheral	739	95	260	533	-65 since 2026-10-07	20	13	2026-09-15
PandaDoc	Mainstream	857	173	373	613	-8 since 2026-10-07	25	13	2026-09-15

Day	Matrix rows reviewed	Players recorded
2026-09-15	63	5
2026-09-16	63	5
2026-09-17	63	5
2026-09-18	63	5
2026-09-19	63	5
2026-09-20	63	5
2026-09-21	63	5
2026-09-22	63	5
2026-09-23	63	5
2026-10-03	63	5
2026-10-04	63	5
2026-10-07	55	5
2026-10-08	50	5

How to read this evidence. A Nishi source mark records whether the named symbol is declared in the selected source file. It does not establish working behavior or accepted delivery. A watching tag names an expected source entry; discovering it updates source coverage only. A dark tag means the file exists but the named symbol was not found: inspect the source and contract before assuming the capability is missing or renaming code. Peer codes are authored assessments; unassessed means no comparison is established, not absence. Qualification, deployment identity, runtime observations and acceptance must carry their own evidence. Adoption records the catalog's observed path through source, build, promotion, registration and invocation; libraries use importer evidence and gates use declared execution surfaces. A full catalog path does not establish quality, freshness or a successful user outcome. Partial and unknown states retain their stated next action. Census stamps: importers asof 1790637268, gate census asof 1790104131 (unix seconds; -1 = census absent).

Capability matrix — measured against source

◉ authored stronger claim; source present● present◐ partial○ absent? unassessed; excluded from relative comparison · click any capability for its evidence

Peer cell coverage: authored assessed 220, unassessed 0. Authored assessments are not verified outcomes.

Capability	Nishi	DocuSign	Clio	NetDocuments	PandaDoc
EDIT
Inline run formatting and images inside a paragraph in the editor DARK — `runtime/nx_office_serve.nx` EXISTS but does not declare `of_inline_runs`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. The editor is a spec-model veneer (H B I P T blocks) over contenteditable; nx_docx already writes runs, tables and PNG drawings (dx_emit_drawing), the UI does not yet expose them rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them watching of_inline_runs Pros none measured yetCons behind DocuSign, Clio, NetDocuments, PandaDoc; open contract; expected source declaration not established	○	●	●	●	●
Structure-preserving Word round-trip -- edit one paragraph, every untouched XML byte identical DARK — `runtime/_hdl_build/nx_docx.nx` EXISTS but does not declare `dx_patch_para`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. The beyond-Google-Docs contract: runs are patched in place inside document.xml so styles, numbering, headers and sectPr survive untouched, provable by nx_contentdiff over the two packages; converters re-serialise the whole document and e-sign vendors flatten to PDF. No rival documents in-place round-trip fidelity dossierwatching dx_patch_para Pros none measured yetCons open contract; expected source declaration not established	○	○	○	○	○
Tracked revisions and comments rendered in the browser view DARK — `runtime/_hdl_build/nx_docx.nx` EXISTS but does not declare `dx_html_track`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. The read side of the row above: dx_to_html gains w:ins, w:del and comments so a redlined draft is reviewable without Word (LP11) rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching dx_html_track Pros none measured yetCons behind Clio, NetDocuments, PandaDoc; open contract; expected source declaration not established	○	○	◐	●	◐
Format-agnostic annotation overlay -- notes, threads, redlines, checklists and signature-field placement, frozen once the envelope completes Source present; authored stronger claim: `nx_ann_add` in `runtime/nx_doc_annotate.nx`, verified at emit. Exceed with the why: the overlay anchors to document, version and page and never parses the file; redlines are additive (a rejected redline is retained, the count never shrinks); required checklist items gate send; and the whole overlay is IMMUTABLE once the envelope is COMPLETED -- proven both by the frozen-flag contract and by driving a real envelope to completed and asserting the add is refused. Rival comments live inside the vendor editor and stay editable after signature (Part) rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `LIB-WIRED importers=8 nonval=3` — fully adopted (top of its ladder). Pros Source symbol found; stronger capability claim is authored; ahead of DocuSign, Clio, NetDocuments, PandaDoc; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	◐	○	◐	◐
Defined-terms and cross-reference consistency (the Litera class of proofing) DARK — `runtime/_hdl_build/nx_proof.nx` EXISTS but does not declare `pf_defined_terms`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. Uncontested by these four; contract-drafting suites sell it separately. Every capitalised defined term must be defined once and used consistently, every cross-reference must resolve (LP22) dossierwatching pf_defined_terms Pros none measured yetCons open contract; expected source declaration not established	○	○	○	○	○
ASSEMBLE
Clause library and templates as data on the immutable plane, fail-closed merge Source present; authored stronger claim: `dg_assemble` in `runtime/nx_docgen_lib.nx`, verified at emit. Exceed with the why: an unknown clause or an unfilled field REFUSES the whole document (never a silent blank in a contract) and the result is a deterministic content-addressed CID reproduced byte-identically across machines (live receipt cid=private-ref:094579ff). Rivals: DocuSign Document Generation [docusign-docgen], Clio Draft templates [clio-draft], NetDocuments document automation [netdocs-docauto], PandaDoc templates [pandadoc-templates] Adoption: `LIB-WIRED importers=5 nonval=4` — fully adopted (top of its ladder). Pros Source symbol found; stronger capability claim is authored; ahead of DocuSign, Clio, NetDocuments, PandaDoc; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	●	●	●	●
Field merge from the matter record Measured: `dg_merge` exists in `runtime/nx_docgen_lib.nx`, verified at emit. Fields resolve from the canonical matter record; a field left unmerged is a refusal, not a warning (dg_unmerged) rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `LIB-WIRED importers=5 nonval=4` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	●	●	●	●
Mail merge -- one Word template times a data table gives N .docx files Measured: `mm_merge_one` exists in `runtime/_hdl_build/nx_mailmerge.nx`, verified at emit. Composes docx_read_part and docx_write_document_xml; placeholders are double-brace fields and must sit inside ONE run (a Word-authored template that splits a placeholder across runs will not merge); PROMOTED and registered 2026-08-18 (LP2). Word's own field codes are the next row [ms-word-mailmerge] Adoption: `REGISTERED-DARK` — PARTIAL: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked). dossiernot adopted: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked) Pros Implementing source symbol found; runtime acceptance separateCons not adopted yet: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)	●	●	●	●	●
Word MERGEFIELD field codes honoured, so a lawyer's existing merge template works unchanged DARK — `runtime/_hdl_build/nx_mailmerge.nx` EXISTS but does not declare `mm_mergefield`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. fldSimple and complex field runs resolved against the data table [ecma-376] [ms-word-mailmerge] (LP13); PandaDoc maps fields in its own editor (Part) dossierwatching mm_mergefield Pros none measured yetCons behind DocuSign, Clio, NetDocuments, PandaDoc; open contract; expected source declaration not established	○	●	●	●	◐
Bulk send -- merged documents become N envelopes in one action DARK — `runtime/nx_doc_envelope.nx` EXISTS but does not declare `nx_env_bulk`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. DocuSign bulk-sends envelopes to multiple signers [docusign-esign]; PandaDoc bulk send [pandadoc-esign]; Clio Draft populates whole document sets but sends per matter (Part) (LP18) dossierwatching nx_env_bulk Pros none measured yetCons behind DocuSign, Clio, PandaDoc; open contract; expected source declaration not established	○	●	◐	○	●
Template registry -- list, version and effective date as first-class data Measured: `dg_tmpl_list` exists in `runtime/nx_tmplstale_lib.nx`, verified at emit. LANDED 2026-08-18 (LP6): ts_tmpl_put snapshots the clause CIDs at put time with an effective epoch, and dg_tmpl_list reads every template as id, version CID of its clause list, and epoch; nx_tmplstale_gate 13 of 13 GREEN, live receipt templates=2 rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `LIB-WIRED importers=2 nonval=1` — fully adopted (top of its ladder). dossier Pros Implementing source symbol found; runtime acceptance separate; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	●	●	●	●
CLERK
Document lineage -- every generated document records the template CID and each clause CID it was built from Measured: `dg_assemble_lineage` exists in `runtime/nx_tmplstale_lib.nx`, verified at emit. LANDED 2026-08-18 (LP7): dg_assemble_lineage assembles through dg_assemble and writes lineage:<docid> = template id, document CID and every clause CID merged; uncontested -- the vendor pages describe template libraries and versioning, not the downstream lineage of the documents produced from them Adoption: `LIB-WIRED importers=2 nonval=1` — fully adopted (top of its ladder). dossier Pros Implementing source symbol found; runtime acceptance separate; ahead of DocuSign, Clio, NetDocuments, PandaDoc; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	○	○	○	○
Template staleness -- a revised clause names every stale template and every client document built from the old text Source present; authored stronger claim: `dg_tmpl_stale` in `runtime/nx_tmplstale_lib.nx`, verified at emit. LANDED 2026-08-18 (LP8), exceed with the why: dg_tmpl_stale compares every snapshot and lineage clause CID against the clause's CURRENT text and prints a WORKLIST (TEMPLATE-STALE and DOC-STALE rows naming template, document, clause, old and new CID), never a count; a worklist that would not fit REFUSES rather than truncating. nx_tmplstale_gate 13 of 13 GREEN with the fresh control (nda, M-002) silent and the detector bite-proven; live receipt stale-before=0 stale-after=2. No rival page documents downstream staleness Adoption: `LIB-WIRED importers=2 nonval=1` — fully adopted (top of its ladder). dossier Pros Source symbol found; stronger capability claim is authored; ahead of DocuSign, Clio, NetDocuments, PandaDoc; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	○	○	○	○
Clause and template governance history -- every put is a new version on the append-only seg-store Measured: `dg_clause_put` exists in `runtime/nx_docgen_lib.nx`, verified at emit. Add or revise a clause = a data change on the immutable plane; who changed what and when is history by construction rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `LIB-WIRED importers=5 nonval=4` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	●	●	●	●
Court forms refresh and staleness watch -- Utah forms re-fetched and hash-compared on a beat Open — watching `runtime/nx_forms_refresh.nx` : `forms_refresh`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. Clio Draft ships always-current fillable court forms for all 50 states [clio-draft] (Best); ours composes nx_research_fetch and nx_filehash over the Utah courts forms index and names each changed form (LP20) dossierwatching forms_refresh Pros none measured yetCons behind Clio (leads); open contract; expected source declaration not established	○	○	◉	○	○
SIGN
Tamper-evident hash-chained signature audit -- each event chained by sha256 over the previous head and the canonical event Source present; authored stronger claim: `se_chain` in `runtime/nx_sign_envelope_lib.nx`, verified at emit. Exceed with the why: every audit event is canonicalised, content-addressed and chained on the sovereign plane, so a holder of the head verifies the whole history without trusting a vendor (tamper at any position is DETECTED, cross-machine determinism proven); DocuSign and PandaDoc keep the certificate and audit trail on their service [docusign-esign] [pandadoc-esign]; Clio Draft collects e-signatures inside Clio (Part); NetDocuments signs through integrations (Part) Adoption: `LIB-WIRED importers=4 nonval=3` — fully adopted (top of its ladder). Pros Source symbol found; stronger capability claim is authored; ahead of DocuSign, Clio, NetDocuments, PandaDoc; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	●	◐	◐	●
UETA and ESIGN consent-gated ceremony -- no recorded consent, no signature Measured: `sc_sign` exists in `runtime/nx_sign_ceremony_lib.nx`, verified at emit. Intent to sign and consent to transact electronically are required fields of the ceremony [utah-ueta-201] [esign-15usc7001]; a signature without them is refused (live receipt no-consent-sign=REFUSED, consent=UETA-OK) Adoption: `LIB-WIRED importers=4 nonval=3` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of NetDocuments; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	●	●	◐	●
Legal-validity verdict per signature -- ESIGN four elements, consumer-consent overlay, eIDAS tier SES/AES/QES Source present; authored stronger claim: `es_ready` in `runtime/nx_esign_lib.nx`, verified at emit. Exceed with the why: readiness is a computed fail-closed predicate (elements AND tier AND audit completeness) graded per signature, not a compliance sentence on a product page; the consumer overlay is ESIGN 7001(c) [esign-15usc7001]. DocuSign and PandaDoc offer AES and QES through partners (Part) Adoption: `LIB-WIRED importers=6 nonval=1` — fully adopted (top of its ladder). Pros Source symbol found; stronger capability claim is authored; ahead of DocuSign, Clio, NetDocuments, PandaDoc; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	◐	○	○	◐
Sealed completion certificate -- CID over envelope, document, signers and audit head Measured: `sc_cert` exists in `runtime/nx_sign_ceremony_lib.nx`, verified at emit. Reproducible from the record itself (live cert_cid=private-ref:8035b8cc); rival certificates are vendor-issued PDFs rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `LIB-WIRED importers=4 nonval=3` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of NetDocuments; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	●	●	◐	●
Sign any office document version in place -- consent-gated ceremony, per-version hash-chained log, sealed certificate served as the receipt Measured: `of_sign_version` exists in `runtime/nx_office_serve.nx`, verified at emit. LANDED 2026-08-19 (LP4): the Sign cell on every version row runs sc_sign over that version's document CID (refused 403 without the UETA and ESIGN consent box -- bite-proven, no certificate is written), chains each signer into v<N>/sign.log under v<N>/sign.head, seals the certificate (CID over envelope, document, signers and audit head) into the version and the immutable sign store, and /cert serves the receipt. Live receipt on the imported Word document: two chained signers, audit head advanced, certificate binds the document CID. Field placement, per-signer links and the signing page are LP10, where DocuSign and PandaDoc are Best. Measured UX constraint: at box load 22 the sign's durable store commit exceeded the 15 s edge window twice while the artifact landed both times, against a quiet-box profile of 129 ms for the same commit -- the box's fsync latency under load, not the ceremony; re-checked 2026-08-19 at load 14.6, where a same-class durable write again exceeded the edge window rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `LIB-WIRED importers=5 nonval=2` — fully adopted (top of its ladder). dossier Pros Implementing source symbol found; runtime acceptance separate; ahead of NetDocuments; fully adopted on the estate ladderCons behind DocuSign (leads), PandaDoc (leads)	●	◉	●	◐	◉
Envelope routing -- ordered signers, CC and approver roles, decline, void, out-of-order refused Measured: `nx_env_send` exists in `runtime/nx_doc_envelope.nx`, verified at emit. Track-D core gated 7 of 7 with negative controls: a signer ahead of routing order is refused, a tampered seal cannot complete, decline is terminal and additive rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `LIB-WIRED importers=9 nonval=3` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of NetDocuments; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	●	●	◐	●
Never-void instrument gate -- a Will routed for e-signature outside an e-wills posture is refused at send and at seal Source present; authored stronger claim: `nx_legal_regime` in `runtime/nx_legal_compliance.nx`, verified at emit. Exceed with the why: ESIGN 7003 and Utah UETA 46-4-103 carve wills out of e-signature law [esign-7003]; Utah recognises electronic wills only under 75-2-1405 (readable as text, signed by the testator, two witnesses in physical or electronic presence) [utah-ewill-1405]; the classifier keys the regime by document type and posture, so the void execution cannot be produced while a compliant e-will still routes. No rival refuses to route a will Adoption: `LIB-WIRED importers=13 nonval=5` — fully adopted (top of its ladder). Pros Source symbol found; stronger capability claim is authored; ahead of DocuSign, Clio, NetDocuments, PandaDoc; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	○	○	○	○
Signature, initial, date and text fields placed on the document, per-signer secure links, signing UI DARK — `runtime/nx_doc_annotate.nx` EXISTS but does not declare `sf_place`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. AN_SIGFIELD already exists in the overlay; the placement UI and per-signer links are the rung (LP10); DocuSign and PandaDoc are the reference here rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching sf_place Pros none measured yetCons behind DocuSign (leads), Clio, NetDocuments, PandaDoc (leads); open contract; expected source declaration not established	○	◉	●	◐	◉
Signer identity verification ladder -- email OTP, SMS, knowledge-based, government ID with document validation DARK — `runtime/nx_sign_ceremony_lib.nx` EXISTS but does not declare `sc_signer_idv`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. DocuSign Identify is the reference [docusign-idv]; the bar for the government-ID leg is NIST SP 800-63A-4 evidence validation and presentation-attack detection [nist-800-63a-4] (LP16) dossierwatching sc_signer_idv Pros none measured yetCons behind DocuSign (leads), Clio, PandaDoc; open contract; expected source declaration not established	○	◉	◐	○	◐
Remote online notarization -- Utah 46-1-3.6 session record with A/V recording and identity evidence Open — watching `runtime/nx_ron.nx` : `ron_session`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. Utah RON (effective 2026-05-06) requires a Utah-located remote notary, sight-and-sound A/V, an ID image and a stored recording [utah-ron-46-1-3-6] through a provider that prints tamper-evident certifications [utah-r623-100-9]; PandaDoc is on the Lieutenant Governor's approved vendor list [utah-ron-vendors] while DocuSign Notary [docusign-notary] is not listed there (Part). Ours is the sovereign record and audit around a commissioned notary, not a notary network (LP17); the 2026 amendments make secondary authentication (dynamic knowledge-based or biometric) part of satisfactory evidence for a remote notarization and set 10-year retention for the journal and the recording [utah-sb139-notary-2026], the provider must run credential analysis with a human visual comparison [utah-r623-100-5], and the federal SECURE Notarization Act remains in committee [secure-notarization-s1561] dossierwatching ron_session Pros none measured yetCons behind DocuSign, PandaDoc; open contract; expected source declaration not established	○	◐	○	○	●
Signed PDF output with an embedded PAdES signature and long-term validation data Open — watching `runtime/nx_pdf_write.nx` : `pdf_sign_pades`, re-measured on every compare beat. Ship that symbol and this mark flips itself; the `comparewatch-` plane row flips with it. There is no sovereign PDF writer today (readers only) -- named honestly; PAdES baseline levels B-B, B-T, B-LT and B-LTA over ISO 32000-2 are the target [etsi-en-319-142-1] (LP15) dossierwatching pdf_sign_pades Pros none measured yetCons behind DocuSign (leads), Clio, NetDocuments, PandaDoc; open contract; expected source declaration not established	○	◉	●	●	●
Utah e-filing connector -- submit through the courts' NDA-gated eFiling API DARK — `runtime/nx_efile_lib.nx` EXISTS but does not declare `efl_submit`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. The filing-date, timeliness and relation-back logic exists (efl_status_pure); the connector needs the courts' non-disclosure agreement and eFiling Integration Guide, which the courts provide to filers building their own interface [utah-efiling] (LP19); Clio integrates e-filing through partners in some states (Part) dossierwatching efl_submit Pros none measured yetCons behind Clio; open contract; expected source declaration not established	○	○	◐	○	○
TRACK
Matter spine plus RPC 1.7 and 1.9 conflicts check Measured: `mt_conflict` exists in `runtime/nx_matter_lib.nx`, verified at emit. Cross-matter adverse-party check by construction on the immutable plane [aba-rule-1-7]; Clio graded Part because its conflict search sits inside case and contact management and the mirrored features page [clio-features] does not name it; NetDocuments is matter-centric with conflicts through integrations (Part) Adoption: `LIB-WIRED importers=35 nonval=28` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of DocuSign, Clio, NetDocuments, PandaDoc; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	○	◐	◐	○
Matter-scoped DMS -- privilege and work-product tags, privilege log, Bates numbering Measured: `box_matter_scan` exists in `runtime/nx_box_lib.nx`, verified at emit. NetDocuments is the legal DMS reference [netdocuments] (Best); ours produces the privilege log from the tags as an e-discovery deliverable and numbers Bates per matter sequentially Adoption: `LIB-WIRED importers=3 nonval=2` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of DocuSign, PandaDoc; fully adopted on the estate ladderCons behind NetDocuments (leads)	●	○	●	◉	○
URCP docketing -- data-driven rules, Rule 6 weekend roll, fail-closed on an unknown rule Measured: `dk_compute` exists in `runtime/nx_docket_lib.nx`, verified at emit. Add a rule = a data change; a calendar deadline landing on a weekend rolls forward; an unknown rule returns -1, never a silent wrong date. Clio ships legal calendaring [clio-features]; whether its court-rules feed covers Utah is not on the mirrored page Adoption: `LIB-WIRED importers=3 nonval=2` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of DocuSign, NetDocuments, PandaDoc; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	○	●	○	○
Time and billing with RPC 1.15 fee application from trust, integer cents Measured: `bl_bill_from_trust` exists in `runtime/nx_billing_lib.nx`, verified at emit. Earned fees move trust to operating only up to the trust balance and a refused billing leaves the trust untouched; Clio billing is the reference [clio-features] (Best); PandaDoc collects payments (Part) Adoption: `LIB-WIRED importers=2 nonval=1` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of DocuSign, NetDocuments, PandaDoc; fully adopted on the estate ladderCons behind Clio (leads)	●	○	◉	○	◐
Trust accounting IOLTA -- no commingling, no overdraw, three-way reconciliation Measured: `trust_disburse_ok` exists in `runtime/nx_trust_lib.nx`, verified at emit. Utah Rule 3-1.15 (records kept five years after the representation ends) [utah-rpc-1-15], Utah IOLTA Rule 4-1001 [utah-iolta-4-1001] and ABA 1.15 [aba-rule-1-15] enforced mechanically; Clio trust accounting is the reference (Best) [clio-features] Adoption: `LIB-WIRED importers=5 nonval=3` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of DocuSign, NetDocuments, PandaDoc; fully adopted on the estate ladderCons behind Clio (leads)	●	○	◉	○	○
New-matter intake -- validate-then-commit composition of conflicts, docket, consent and retainer Source present; authored stronger claim: `intake_new_matter` in `runtime/nx_matter_intake_lib.nx`, verified at emit. Exceed with the why: all compliance gates fire BEFORE any write, so a refused intake leaves ZERO partial state (no half-open matter, no orphan retainer); Clio Grow intake and Draft questionnaires gather the data [clio-draft]; PandaDoc forms (Part) Adoption: `LIB-WIRED importers=2 nonval=1` — fully adopted (top of its ladder). Pros Source symbol found; stronger capability claim is authored; ahead of DocuSign, Clio, NetDocuments, PandaDoc; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	◉	○	●	○	◐
Contract lifecycle -- auto-renewal trap flagged, obligations overdue, fail-closed on unknown terms Source present; authored stronger claim: `clm_renewal_state` in `runtime/nx_clm_lib.nx`, verified at emit. Exceed with the why: the missed cancellation window is a hard state that cannot be reported as safe; DocuSign surfaces agreement dates across its IAM platform [docusign-esign]; PandaDoc CLM (Part) Adoption: `LIB-GATE-ONLY importers=1` — PARTIAL: imported only by validation organs (gates, tests, benches): wire it into a shipping program. not adopted: imported only by validation organs (gates, tests, benches): wire it into a shipping program Pros Source symbol found; stronger capability claim is authored; ahead of DocuSign, Clio, NetDocuments, PandaDocCons not adopted yet: imported only by validation organs (gates, tests, benches): wire it into a shipping program	◉	●	○	○	◐
Playbook redline risk -- deviation from the standard clause scored, auto-approve only inside the band Measured: `cl_risk_pure` exists in `runtime/nx_clause_lib.nx`, verified at emit. cl_best_match finds the governing clause, cl_deviation_permille scores the distance and cl_auto_approve_pure closes only inside the declared band; DocuSign agreement AI (Part) rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `LIB-WIRED importers=6 nonval=5` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of DocuSign, Clio, NetDocuments, PandaDoc; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	◐	○	○	○
Work-done trail -- every save, restore and share event on the append-only manifest with a served diff Measured: `of_diffpage` exists in `runtime/nx_office_serve.nx`, verified at emit. The trackability the operator asked for is the manifest itself: usec-stamped versions, restore-as-new-version, ReBAC share and unshare tuples, and /diff of any two versions rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `LIB-WIRED importers=5 nonval=2` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	●	●	●	●
PORTAL
Client workspace routes -- envelopes, status, checklist, document fetch, staff view, deny-by-default Measured: `lp_handle` exists in `runtime/nx_legal_portal.nx`, verified at emit. Gated over a real socket (loopback live gate) with a wet-signature-required Will surfaced rather than offered to sign; the daemon is BUILT and UNPROMOTED on loopback, so this row is measured present while NOT yet served -- the next row is the deploy rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `LIB-WIRED importers=6 nonval=2` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; fully adopted on the estate ladderCons behind Clio (leads)	●	●	◉	●	●
Client portal served on the firm domain with the docportal realm and HTML views DARK — `runtime/_hdl_build/nx_legal_portal_daemon.nx` EXISTS but does not declare `lpd_serve_realm`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. portal.andelinwest.com over the andelinwest_docportal realm, HTML views over lp_handle, per-tenant file-backed stores (LP9) rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them dossierwatching lpd_serve_realm Pros none measured yetCons behind DocuSign, Clio (leads), NetDocuments, PandaDoc; open contract; expected source declaration not established	○	●	◉	●	●
Firm office workspace mounted on the firm domain with the client realm Measured: `od_session` exists in `runtime/_hdl_build/nx_office_daemon.nx`, verified at emit. LANDED 2026-08-19 (LP3): ONE nx_office_daemon binary takes port, keys, store, realm, root, base, uid index, closed mode and authz prefix from argv, and od_session resolves the andelinwest_docportal session to the firm handle. Live at admin.andelinwest.com/office in closed mode, verified over the edge: 401 unauthenticated, invited login 200 with an owned save, and the firm document 404 on the public nishifamily office; nx_office_closed_gate 16 of 16 GREEN re-run after the deploy. The shared open-mode office namespace is never exposed to a law firm rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: `RUN-BY:daemon` — fully adopted (top of its ladder). dossier Pros Implementing source symbol found; runtime acceptance separate; ahead of DocuSign; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	○	●	●	●
Secure client messaging on the firm domain -- no-cookie webmail, per-user mailboxes Measured: `epd_handle` exists in `runtime/_hdl_build/nx_email_portal_daemon.nx`, verified at emit. LIVE at mail.andelinwest.com on the same Modern Auth as the vault; Clio secure messaging [clio-portal] Adoption: `LIVE-DAEMON` — fully adopted (top of its ladder). Pros Implementing source symbol found; runtime acceptance separate; ahead of DocuSign, NetDocuments, PandaDoc; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)	●	○	●	○	○
AI
Contract review grounded on the clause library with cite-or-abstain DARK — `runtime/nx_clause_lib.nx` EXISTS but does not declare `cl_review`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. The bar: in the Vals Legal AI Report the lawyer baseline beat every AI tool on redlining (79.7 versus 59.4 and 53.6 percent) [vals-vlair], and leading legal research tools cited unsupported law in a large share of answers [magesh2024]; a review that can only propose text traceable to a governed clause, and abstains otherwise, is the design answer (LP21) dossierwatching cl_review Pros none measured yetCons behind DocuSign, Clio, NetDocuments, PandaDoc; open contract; expected source declaration not established	○	●	●	●	●
SIGN
Execution ladder keyed by instrument and Utah statute -- e-will under 75-2-1405 and 75-2-1408, trust or power of attorney or directive under 75-13-206 and 75-13-207, ESIGN 7003 carve-out otherwise DARK — `runtime/nx_legal_compliance.nx` EXISTS but does not declare `lr_exec_ladder`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. Extends nx_legal_regime: the classifier already knows DT_WILL through DT_ADVANCE_DIRECTIVE and the wet-versus-e-wills regimes; the ladder adds the Utah 2026 rule set as DATA (which instrument needs two witnesses in physical or electronic presence, which takes an authorized officer's electronic signature for notarization, which needs the self-proving affidavit, which is excluded outright) so a ceremony is refused before send unless every statutory element is scheduled [utah-hb181-ueepda] [utah-ewill-1405] [utah-ewill-1408] [esign-7003]. No rival keys its ceremony to the instrument type; each signs whatever is uploaded (LP23) dossierwatching lr_exec_ladder Pros none measured yetCons open contract; expected source declaration not established	○	○	○	○	○
Remote witnessing session -- electronic presence for the two witnesses of an e-will or the attesting individual of a non-testamentary document, with the real-time A/V record sealed into the audit chain DARK — `runtime/nx_sign_ceremony_lib.nx` EXISTS but does not declare `sc_witness_session`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. Utah defines electronic presence as two or more individuals in different locations communicating in real time to the same extent as if physically present [utah-hb181-ueepda] [utah-ewill-1405]; the session record names each witness, the ceremony head each attested and the recording reference, and a will whose witnesses did not sign within a reasonable time reads NEEDS-MORE never VALID. The rivals' witnessing is their notary product or nothing (LP24) dossierwatching sc_witness_session Pros none measured yetCons open contract; expected source declaration not established	○	○	○	○	○
Signer identity through Utah SEDI or an ISO mDL presented over the browser's Digital Credentials API -- selective disclosure, no card image stored DARK — `runtime/nx_sign_ceremony_lib.nx` EXISTS but does not declare `sc_idv_sedi`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. Chrome 141 and Safari 26 ship the Digital Credentials API for wallet presentation through the browser [chrome-dc-api] [webkit-dc-api]; Utah's state-endorsed digital identity mandates selective disclosure, a right to be free from tracking through presentations, minimum-attribute processing by relying parties and acceptance of a digital guardian's presentation [utah-sb275-sedi] [utah-sedi-guide]; the leg records only the attribute names the ceremony needs and the verifier result, never the credential. Rivals verify by ID-document upload and knowledge questions [docusign-idv] and none documents a wallet presentation (LP25) dossierwatching sc_idv_sedi Pros none measured yetCons open contract; expected source declaration not established	○	○	○	○	○
Certified paper copy of an electronic instrument -- the 75-13-209 affirmation for a trust or power of attorney and the e-will officer certificate, printed with the audit head and certificate CID DARK — `runtime/nx_sign_ceremony_lib.nx` EXISTS but does not declare `sc_paper_certify`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. A court, a bank or a county recorder may still want paper; the copy carries the affirmation under penalty of perjury the statute names [utah-hb181-ueepda] and the content-addressed head, so the paper can be checked against the record it came from. Rivals print a PDF with a vendor certificate page (LP26) dossierwatching sc_paper_certify Pros none measured yetCons open contract; expected source declaration not established	○	○	○	○	○
PORTAL
Mobile-first signing and review surface -- one-thumb ceremony, WCAG 2.2 AA target size and accessible authentication, no app install, on the phone the client already holds DARK — `runtime/_hdl_build/nx_legal_portal_daemon.nx` EXISTS but does not declare `lpd_mobile_ceremony`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. Most e-signatures now complete on a phone and the rivals' mobile signing is their strongest surface (DocuSign and PandaDoc Best); the sovereign bar is WCAG 2.2 AA measured by nx_uiq_atree and nx_uiq_perf on the served page: 24 by 24 CSS pixel targets, no dragging, no redundant entry, and an accessible-authentication path that never asks the client to transcribe a code [wcag22] (LP27) dossierwatching lpd_mobile_ceremony Pros none measured yetCons behind DocuSign (leads), Clio, NetDocuments, PandaDoc (leads); open contract; expected source declaration not established	○	◉	●	●	◉
Passkey login with family-quorum and succession recovery -- device biometric, K-of-N trusted contacts, attestation-gated succession and a proof-of-life veto window DARK — `runtime/_hdl_build/nx_social_auth_recover.nx` EXISTS but does not declare `pk_login`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. The recovery ladder exists as gated libs (nx_sar_recover, nx_succession_recover, nx_dm_status) and no daemon composes them; the browser leg is WebAuthn as last-mile interop with sovereign verification, measured against NIST SP 800-63B-4 phishing-resistant AAL2 with syncable passkeys [nist-800-63b-4]. Rivals offer a password plus SMS or SSO (Part); none documents family recovery or succession (LP28) dossierwatching pk_login Pros none measured yetCons behind DocuSign, Clio, NetDocuments, PandaDoc; open contract; expected source declaration not established	○	◐	◐	◐	◐
Living estate vault -- the client's signed instruments, the fiduciary roster and a release rule that hands the right documents to the trustee, personal representative or beneficiaries on a proven death event DARK — `runtime/nx_legal_portal.nx` EXISTS but does not declare `lp_vault_release`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. Utah Code 75-7-811 obliges the trustee to tell qualified beneficiaries of the trust and their right to a copy within 60 days of learning of the death, and Utah Bar Opinion 23-01 finds the drafting lawyer impliedly authorized to furnish the instruments the fiduciary has not [utah-eaoc-23-01]; the release composes the attestation-gated succession recovery and the dead-man veto so a living client on a long trip is never succeeded, every release is a chained audit event, and retention is DATA (a remote-notarization recording 10 years [utah-sb139-notary-2026], trust records five years [utah-rpc-1-15]). Consumer estate platforms sell a vault; none of the four rivals documents one (LP29) dossierwatching lp_vault_release Pros none measured yetCons open contract; expected source declaration not established	○	○	○	○	○
SIGN
Every Utah execution element answered by the law engine -- witness presence, notarization means, self-proving, the remote-notarization record and its retention, the certified paper copy and record retention, each a typed topic filled from the enrolled bills DARK — `runtime/nx_law_core.nx` EXISTS but does not declare `lr_exec_elements`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. WATCH (LP30): one typed topic per execution question filled for US-UT from the enrolled bills and code sections already pinned here [utah-hb181-ueepda] [utah-sb139-notary-2026] [utah-ewill-1405], the deciding sentence quoted as an exact byte span of its mirror; lr_exec_elements(instrument, place, day) asks the one law engine (legal LG4) and nx_legal_compliance keeps no regime table of its own. No rival page keys a ceremony to the instrument's statutory elements; each signs whatever is uploaded [docusign-esign-oct] (No by evidence) dossierwatching lr_exec_elements Pros none measured yetCons open contract; expected source declaration not established	○	○	○	○	○
ASSEMBLE
Every document carries its instrument class -- will, codicil, trust, trust power, durable power of attorney, directive, guardian nomination, disclaimer, deed or other, recorded from the template that produced it DARK — `runtime/nx_tmplstale_lib.nx` EXISTS but does not declare `dg_instrument_class`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. WATCH (LP31): dg_assemble_lineage records the class; an imported document takes a class only by an explicit recorded choice of a firm handle; an unclassified document receives the strictest line (view only, no electronic ceremony offered) and a reclassification is a new audit event that never rewrites the old one. The rivals' templates carry no legal instrument class that gates a ceremony [docusign-docgen] [clio-draft] [netdocs-docauto] [pandadoc-templates] (No by evidence) dossierwatching dg_instrument_class Pros none measured yetCons open contract; expected source declaration not established	○	○	○	○	○
SIGN
One requirement set for a ceremony that touches several states -- the strictest sourced line over the signer's domicile, the signer's location, each witness's place and the notary's commissioning state DARK — `runtime/nx_law_core.nx` EXISTS but does not declare `lr_exec_resolve`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. WATCH (LP32): composes the engine's several-places answer (legal LG5) and returns one element set with every contributing law row named; with no sourced recognition row the set is the strictest over every place, so a ceremony is offered only where every place's law permits it. No rival page documents a multi-state execution resolver (No by evidence) dossierwatching lr_exec_resolve Pros none measured yetCons open contract; expected source declaration not established	○	○	○	○	○
CLERK
Electronic-execution jurisdictions read into the registry from each state's own code -- one row per topic with the section, the quoted deciding sentence, effective and sunset dates DARK — `runtime/nx_law_core.nx` EXISTS but does not declare `xl_wave_electronic`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. WATCH (LP33): the set of states whose statute authorizes an electronic will or an electronic non-testamentary instrument is READ from each code, with the Uniform Law Commission enactment kit and one independent survey as second and third witnesses and every disagreement named; the coverage partition over the fifty-one codes is printed (legal LG6). No rival page documents a sourced per-state execution registry (No by evidence) dossierwatching xl_wave_electronic Pros none measured yetCons open contract; expected source declaration not established	○	○	○	○	○
Every remaining jurisdiction's paper execution law read into the registry -- witness count and qualification, notarization, the self-proving affidavit and every other recognized form DARK — `runtime/nx_law_core.nx` EXISTS but does not declare `xl_wave_paper`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. WATCH (LP34): each remaining state's electronic topics carry a row naming the wills act section read and recording that it authorizes no electronic execution, so a refusal rests on a statute that was read; coverage reads rowless 0 and unsourced 0 over the fifty-one codes. No rival page documents it (No by evidence) dossierwatching xl_wave_paper Pros none measured yetCons open contract; expected source declaration not established	○	○	○	○	○
PORTAL
A state's ceremony opens only on the acceptance of an attorney licensed there -- an accept-plane row naming the bar number, the day and the law rows reviewed by id and pin DARK — `runtime/nx_legal_portal.nx` EXISTS but does not declare `lp_state_enable`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. WATCH (LP35): sourced rows alone open the requirement view and never a ceremony; an acceptance is void once any reviewed row drifts or is superseded (legal LG7). No rival page documents a licensed-attorney gate on a state's ceremony (No by evidence) dossierwatching lp_state_enable Pros none measured yetCons open contract; expected source declaration not established	○	○	○	○	○
CLERK
Statutory forms per state in the template registry with a staleness watch -- the self-proving affidavit, a statutory power of attorney and a directive form, byte-compared with the pinned statute on a beat DARK — `runtime/nx_tmplstale_lib.nx` EXISTS but does not declare `tmpl_state_forms`: something shipped at this path under another name, and this mark would read open forever. Repoint the contract to the real entry point (the plan rung AND this row) or rename the function; the flip follows on the next beat, and the `comparewatch-` plane row reads DARK until then. WATCH (LP36): keys a template by jurisdiction and instrument class and names every template and every client document built from a changed statutory form (the LP8 staleness worklist extended to statutes). Clio Draft ships always-current fillable court forms for all 50 states [clio-draft] (Best); the others document template libraries, not statutory forms (No by evidence) dossierwatching tmpl_state_forms Pros none measured yetCons behind Clio (leads); open contract; expected source declaration not established	○	○	◉	○	○

Capabilities measured on other boards

Graded once, on the home board. Each row below is a row of another board, where it is measured against the rivals that sell the capability; this board references it and never re-grades it. The cells and the column names are the home board's, copied at publish; the Nishi mark is measured with the same source ruler the home page uses. A reference whose home row cannot be read says so by name and is never folded into open or present.

Capability (home: unidoc)	Nishi	Google Drive	Microsoft 365 web	Adobe Acrobat web	Nextcloud Hub	Note
OPEN: Word .docx read -- own OPC/ZIP reader, text runs extracted docx_read_text	PRESENT	YES	YES	NO	PART	The Word text-extraction stage (own OPC/ZIP reader over the OOXML package [ecma-376]) is graded on /compare/unidoc against the document portals, moved there 2026-10-07; on this board every practice rival opens Word uploads (Clio Draft converts existing Word files into reusable templates [clio-draft]), which the home grading covers
OPEN: Word .docx opened as a page (paragraphs, headings, tables) dx_to_html	PRESENT	YES	YES	NO	PART	Word rendered in the browser is a document capability graded on /compare/unidoc against the office rivals; on this board it is a reference (every practice rival opens Word uploads [clio-draft], which the home grading already covers)
OPEN: OpenDocument .odt opened as a page odt_read_text	PRESENT	YES	YES	NO	PART	OpenDocument read and write is graded on /compare/unidoc against the office rivals [odf-1-3]; the 2026-10-07 rival census read No by evidence for every practice rival (no mirrored practice page mentions OpenDocument), so this board references the home grading
PORTAL: Import a Word or ODF file as a versioned document of_import	PRESENT	YES	YES	NO	YES	Import of a Word or ODF file as a versioned document is graded on /compare/unidoc against the document portals; rung LP1 landed it 2026-08-19 (POST /import keeps the ORIGINAL bytes as v1 and serves them untouched until the first edit, extracts the spec through the format organ's spec verb, refusals name themselves: 409 duplicate name, 415 not a package, 413 above the named ceiling, 400 no file part; a genuine Word document of 25 parts imported live, original byte-identical sha 10b848ad, nx_office_import_sign_gate 28 of 28 GREEN), and every practice rival opens uploads, which the home grading covers; the rung is mapped here by reference
OPEN: Paragraph-faithful Word extraction -- headings, paragraphs and table rows kept as structure, not a run soup docx_read_spec	PRESENT	YES	YES	NO	PART	Paragraph-faithful Word extraction (the spec verb the import consumes: headings, paragraphs and table rows kept as structure, not a run soup) is graded on /compare/unidoc against the document portals, moved there 2026-10-07; every practice rival opens Word files and the home grading covers it, and the practice-specific capabilities over an imported file on this board are the ceremony and the law-clerk desk
OPEN: PDF opened as a page -- text layer reflowed, figures and layout not painted pf_to_html	PRESENT	YES	YES	BEST	YES	PDF text extraction and the reflow view are graded on /compare/unidoc against the office rivals; the 2026-10-07 rival census read NetDocuments No by evidence on this board (neither mirrored NetDocuments page mentions PDF; its features page is queued), and the signed-PDF writer this practice needs is the SIGN row below, not this reference
INTERACT: Edit as a new version, restore as a new version, diff served of_save	PRESENT	YES	PART	NO	YES	The append-only versioned editor (every save a new version, restore as a NEW version, the diff of any two versions a served page) is graded on /compare/unidoc against the office rivals; on this board the practice-specific capability over those versions is sign-in-place, the of_sign_version row below (LP4). The practice rivals read: NetDocuments and PandaDoc keep version history inside the vendor store where it is a mutable feature; Clio Draft hands editing to Word
INTERACT: Real-time co-editing inside the office of_coedit	OPEN	BEST	BEST	NO	YES	Real-time co-editing inside the office (the RGA text CRDT cd_live_sync, built and gated in nx_coedit.nx and not yet imported by the office) is graded on /compare/unidoc, whose rung UD8 shares this contract; rung LP14 is mapped here by reference and is to be retired onto unidoc:UD8 through the lifecycle; the practice reading on this board was NetDocuments co-authoring through Word (Yes) and PandaDoc collaborating in its editor (Yes), DocuSign and Clio No
PORTAL: The vault index is the file browser -- a page listing documents by matter and folder with search dad_handle	PRESENT	BEST	BEST	YES	BEST	The vault index served on the firm's own host (invite-gated OPAQUE login, no cookies, private uploads proven absent from public search, LIVE at admin.andelinwest.com) is graded on /compare/unidoc against the document portals; the practice reading on this board was Clio for Clients as the portal reference [clio-portal] (Best), and the practice-specific portal rows are lp_handle and lpd_serve_realm below (LP9)
SECURE: Byte-exact original always served beside the page, header-injection safe nx_doc_serve_response	PRESENT	YES	YES	YES	YES	Byte-exact document delivery (Content-Length framing that round-trips embedded CRLFCRLF and NUL bit-for-bit, header-injection-safe filenames, unknown types downloading rather than rendering) is graded on /compare/unidoc; every practice rival serves document downloads and the home grading covers it
SOV: On the family's own hardware, no telemetry -- documents never leave the host dv_ext	PRESENT	NO	NO	NO	YES	On-premise with no telemetry is a PROPERTY graded once, on /compare/unidoc (where Nextcloud is also self-hosted and the three cloud rivals are not); for a practice it is a duty rather than a feature: ABA Formal Opinion 512 (July 2024) makes confidentiality of client information entered into AI tools an explicit duty [aba-op-512], and none of the four practice rivals is self-hosted

Capability (home: office)	Nishi	Microsoft365	Workspace	LibreOffice	OnlyOffice	Note
Tracked revisions dx_emit_track	PRESENT	YES	YES	YES	YES	Tracked revisions written as real w:ins and w:del [ecma-376] are graded on /compare/office against the office suites; the practice reading on this board was DocuSign PDF-centric (No), Clio Draft handing the file to Word (Part), NetDocuments editing through Word (Yes) and PandaDoc in-editor suggestions rather than OOXML revisions (Part); the read side, a redlined draft reviewable without Word, is the dx_html_track row below (LP11)
Comments and annotations dx_cm_add	PRESENT	YES	YES	YES	YES	Comments anchored in the .docx package (commentRangeStart and End plus commentReference [ecma-376]) are graded on /compare/office; every practice rival comments inside its own editor, and the practice-specific thread, redline and checklist overlay that never parses the file is the nx_ann_add row below
Grammar and style proofing pf_check	PRESENT	YES	YES	YES	YES	Rule-based grammar checks and the corpus-derived spell check are graded on /compare/office against the office suites; the practice reading on this board was No on DocuSign, Clio and NetDocuments and Part on PandaDoc, and the proofing a contract needs beyond grammar is the defined-terms row below (LP22)
In-document AI drafting of_llm_complete	PRESENT	BEST	BEST	NO	NO	In-document drafting on the sovereign no-float seat is graded on /compare/office against Copilot and Gemini; the practice assistants (DocuSign IAM, Clio Duo, NetDocuments ndMAX, PandaDoc AI) all read Best against a 0.5B seat, and the practice-specific answer is the cite-or-abstain contract review row below (LP21), not a larger model

xrows declared=15 resolved=15 norow=0 noboard=0 badrow=0 (partition sums)

Rival-claim provenance. Every Yes, Best or Part mark in a rival column is a claim about someone else's product. A cited row carries a reference mark that resolves to a pinned mirror (the refs gate measures that); an uncited row is an observation read and is badged in its evidence until a reference lands. The badge is the receipt, never the proof: a mark proves a mirror exists, not that the mirror supports the code. The rows are counted below.

Rival claims, counted
Class	Count	Note
rows with rival marks	39	rows carrying a Yes, Best or Part in a rival column
cited	24	a reference mark resolves to a pinned mirror
uncited	15	an observation read, badged until a reference lands
rows, summed	39	RECONCILED: the parts sum to the total 39

Delivery and evidence

Inspect risks, technical debt, rendered observations, experiments and references. Read scope and limitations alongside every result.

Risk register

Risk	Likelihood x impact	Mitigation
A ceremony that lets a will route without both witnesses scheduled in electronic presence produces a void instrument that reads signed	possible x high	LP23 done-rule: NEEDS-MORE never VALID until every statutory element is recorded; LP24 seals the witness session into the chain.
Storing a card image or a full credential for identity verification creates the over-collection S.B. 275 forbids a relying party	possible x high	LP25 done-rule: attribute names and the verifier result only; the gate asserts no image bytes in the event.

Release history and work log

The worked plan, on the board. Every leg appends what it measured, landed, retracted, learned and left queued, per rung, so a crash leaves the next seat a ledger here rather than a transcript to mine. Kinds: measure, land, retract, lesson, queue. Newest last.

When	Rung	Kind	Entry
2026-09-03	LP9	measure	nx_compare_rank legalpractice on 2026-09-03: rungs=21 done=7 open=14, target version 1.0, critical path LP11 (4800) then LP10 (1600) then LP13 (1600) then LP9 (800) then LP12 then LP14; LP2 reads FINISH REGISTERED-DARK (nx_mailmerge and nx_odt never invoked over MCP); LP14 read UNMAPPED because the co-editing matrix row carried cd_live_sync, corrected the same day to the _ABSENT_:of_coedit watch on nx_office_serve
2026-09-03	LP9	measure	nx_catalog on 2026-09-03: nx_legal_portal_daemon BUILT and STAGED 143427 B, not promoted, not registered; nx_legal_portal, nx_legal_store, nx_doc_envelope, nx_doc_annotate, nx_doc_seal, nx_doc_serve and nx_legal_compliance are libs (adoption is importer count); nx_sign_ceremony and nx_sign_envelope REGISTERED-DARK; nx_office_daemon PROMOTED-UNREGISTERED which is correct for a daemon; nx_ron, nx_pdf_write and nx_forms_refresh absent exactly as their watch rows declare
2026-09-03	LP23	lesson	The execution ladder on this board was written against 2020 law: H.B. 181 (effective 2026-05-06) moved trusts, powers of attorney and directives out of the general UETA regime into a dedicated one with electronic presence for witnesses and an electronic-signature notarization, and S.B. 139 (same date) added secondary authentication to remote-notary identity and a 10-year recording retention; a ceremony keyed only to will-versus-not-will is a year behind the statute it enforces
2026-09-03	LP25	measure	September 2026 research banked as refs: Chrome 141 and Safari 26 ship the Digital Credentials API; Utah S.B. 275 creates the state-endorsed digital identity with a digital guardian and selective disclosure and repeals the electronic license certificate on 2027-01-01; NIST SP 800-63B-4 final since July 2025; the federal SECURE Notarization Act is still in committee; no rival page documents a wallet presentation, so LP25 is a lead nobody holds
2026-09-03	LP27	queue	Build order for the doc-portal lane now that the board carries L3: LP10 signing UI (fields, per-signer links) and LP27 the mobile ceremony on the same page, then LP9 promote the portal daemon with file-backed stores behind portal.andelinwest.com (opening a public surface is the operator's call), then LP28 passkey and recovery, then LP23 and LP24 for e-wills, then LP25 SEDI; LP11 and LP13 stay on the office lane; the foundational byte-up work (PDF writer LP15, e-filing LP19) is the other lane's
2026-09-03	LP9	measure	box at landing: load 18.87 against admission ceiling 40.00, D-state 7 (jbd2, nx_secret_scan, two nx_store_put, nx_web_shard_compact, nx_nav_sentinel, synostgd-disk), zombies 24; builds admissible by the ceiling, but sync MCP reads still 503 on the edge window (nx_catalog twice), so every census here ran through nx_job_run and read its artifact
2026-09-03	LP9	land	Board landed and gated 2026-09-03: legalpractice.refs 19182 to 31437 B (15 rows, pins verified by nx_compare_refs_gate: mirrors-exist PASS, pins-match-filehash 1234 of 1234 PASS, declared-refs-cited-inline PASS; the one RED tooth left in the estate register is deploy.matrix key vercel-deploys, another lane's), legalpractice.matrix 24960 to 31253 B (63 rows, 7 new watch rows, the UNPINNED bars declared in the header), legalpractice.plan 14029 to 24883 B (L3, LP23 to LP29, 6 bars, 2 risks); nx_domain_admit legalpractice went REFUSE (no barcheck row and no UNPINNED declaration) to ADMIT with rows=63 grounded=41 absent=19 ungrounded=0; still owed there: C4 never-bitten nx_tmplstale_gate and nx_office_closed_gate, C5 second method class ABSENT
2026-09-03	LP9	queue	Cross-board 2026-09-03: /compare/unidoc admitted the same day and its rung UD3 (dad_unidoc: GET /doc/<cid> served by the portal daemon through ud_render_path, POST annotate and sign composing nx_ann_add and of_sign_version) is the SAME daemon work as LP9 and the client-facing half of LP10 -- the unified page (nx_unidoc, promoted 50f18daf, gate 30 of 30) is the surface the firm's client sees a will or trust on, with the consent-gated sign form already emitted as a plain form; build UD3 once and both boards flip
2026-09-25	LP28	queue	PM seat: authz AZ9 wauth_assert_verify (declared this hour from operator goal child R10 1790355010) is the estate-wide WebAuthn Level 3 verifier on the family realm, so LP28 should compose it for the portal passkey login rather than build a second authenticator-signature verifier inside nx_legal_portal_daemon; the family-quorum and succession recovery (nx_sar_enroll_split, nx_sar_recover, nx_succession_recover) stay LP28 own
2026-09-28	LP23	queue	INTAKE 1790633100 routed by nx_intake_route (law-core-seat, epoch 1790633062) from operator: for the law domain are we making sure that these things are tightly coupled but that we can use them for import export etc so that we can have our compliance and ethics and legal and all that nailed d -- sponsor intake-1790633100 plus2
2026-09-28	LP23	queue	HOW THE ONE LAW ENGINE SERVES LP23 (legal LG4 shipped 2026-09-28: nx_law_core law_ask over knowledge/law/, gate nx_law_core_gate 86/86, CLI nx_law on MCP): the execution ladder becomes rows of knowledge/law/esign.will.conf, esign.nontestamentary.conf and esign.deed.conf (topics already catalogued: electronic as the enum permitted, permitted-with-formalities, refused, and witnesses as an int, both max-direction, no world row), one row per jurisdiction and statute with its enrolled-bill mirror, pin and the deciding sentence quoted (Utah H.B. 181 UEEPDA for trusts, powers of attorney and directives from 2026-05-06; 75-2-1405 and 75-2-1408 for electronic wills), so nx_legal_compliance asks law_ask(esign.<class>, jurisdiction, day) instead of taking a caller flag over a 2020-law regime table; an unread jurisdiction reads the strictest line (refused, the most witnesses), never a clearance; the knowledge/legal_exec_ladder.conf this rung names is exactly those three files, so no second table is created. Recipe owner legalpractice LP23, engine owner legal LG4 (RACI law-core, legal A).

Risk register

Risk	Likelihood x impact	Mitigation
A state's rows are written from a uniform act's text or from a survey instead of that state's enacted code, and a non-uniform amendment makes the ceremony wrong for that state	likely x high	LP33 and LP34 done-rules: every row quotes the state's own code from a pinned mirror; the uniform act and the survey are second and third witnesses whose disagreements are named, never the source of a row.
A ceremony that touches two states is validated under one state's law only and the instrument is void where it is probated	possible x high	LP32 done-rule: the strictest line over every place involved unless a sourced recognition row relaxes a named element; LP35 keeps a state's ceremony closed until an attorney licensed there has accepted the rows.
A statute changes in a legislative session and the pinned row keeps answering the old law	likely x high	legal LG7 names the drifted row and the engine answers the strictest line until it is re-read; an enacted law not yet in force is a pending row with its effective date.

Release history continued

When	Rung	Kind	Entry
2026-10-03	LP30	measure	2026-10-03 opening measurement for the Utah-then-every-state program: nx_compare_rank legalpractice rungs=28 done=7 open=21, target version 1.0, critical path LP9 then LP10 then LP11 then LP13 then LP14 then LP12, LP23 seventh with sponsor plus2; nx_barfresh NO-BAR, nx_ladder NO-LADDER (28 rungs unplaced), treatment undeclared, XDEP edges=0; nx_catalog: nx_legal_portal_daemon still BUILT and STAGED 143427 B and unpromoted (the stage is a month old), nx_docportal_admin_daemon LIVE 1744488 B, nx_doc_view REGISTERED with no cap minted, nx_sign_ceremony, nx_sign_envelope, nx_legal_svc and nx_docgen REGISTERED-DARK, nx_law_core and nx_legal_compliance libs; knowledge/law lists 16 files (trade topics, topics.conf, jurisdictions.conf) and no esign file, so every execution topic refuses no-table for every place; nx_compare_rank unidoc rungs=9 done=1, UD3 the portal route still open and UD2 and UD9 unmapped
2026-10-03	LP33	measure	Researcher reach for the state census, measured 2026-10-03: nx_research_fetch read the Uniform Law Commission Electronic Wills Act page (status 200, 107722 B, mirror knowledge/fetched/rf_6f764188.raw, sha256 41308e392c05836a24502965e4d91bf002af7dd6a3304a4dc775d34079fb1bdf) and the mirror carries the enactment kit and final act links but NO enactment list: the map is a Power BI frame the fetcher cannot read (the string Utah occurs 0 times in the body). So the census of which states enacted what is read from each state's own code, with the enactment kit document as a second witness; secondary web pages read the same day disagree with one another on which states adopted the uniform text, which is the reason no state list is written on this board before it is read from primary sources
2026-10-03	LP30	queue	Build order for the program (the ranker decides within it): (1) LP23 the three esign files with US-UT rows from the pinned mirrors, then LP30 the element topics and lr_exec_elements; (2) unidoc UD3 the portal route and unidoc UD10 the requirements panel, so the page a client opens states what the instrument needs and under which section, with LP31 the instrument class so the panel knows what it is looking at; (3) legal LG6 coverage and LG5 the several-places answer, then LP32; (4) LP33 the electronic-execution jurisdictions, LP34 every remaining jurisdiction, LP36 the statutory forms, with legal LG7 the drift watch running before the second state lands; LP35 opens a state's ceremony only on an attorney's acceptance. Owed before any of it is called SOTA: this board's dated bars and ladder (three independent current witnesses per bar: the state codes and uniform acts as the standard, a standards source for identity and signature format, and the rivals' current product pages labelled vendor claims), and the October attestation of the legal board's bar. The estimates for LP33 and LP34 are provisional: the cost per jurisdiction is measured on Utah first and the two figures are re-derived from it
2026-10-03	LP35	queue	OPERATOR DECISIONS this program waits on, none of which blocks the Utah stage: (a) the delivery posture outside Utah -- the firm's own practice where its lawyers are admitted, or a platform an attorney licensed in each state operates; the law engine answers execution law either way, and the posture becomes its own sourced topic before any non-Utah ceremony opens; (b) whether a state's ceremony requires the LP35 acceptance by an attorney licensed there (proposed: yes, with sourced rows alone opening the requirement view only); (c) which daemon carries the client's document URL -- the live vault daemon (unidoc UD3) or the staged legal portal daemon (LP9) -- to be settled by reading both sources before either is deployed, since two portals for one client is the duplicate this board exists to prevent; (d) opening portal.andelinwest.com stays the operator's call as recorded on 2026-09-03
2026-10-03	LP30	retract	The seven watch rows for LP30 to LP36 were appended to legalpractice.matrix with all four rival cells unassessed (code 4) and withdrawn within the hour: the emitter rightly refuses to draw a position map while any peer cell is unassessed, so the page published at 1791044729 read Position map unassessed, 28 peer cells, where the page before it carried the map. The matrix is back to its 31253 bytes and the rungs stay on this plan, reading UNMAPPED until each row returns with its rival cells assessed from cited pages. Lesson: a watch row costs the page its comparative figure unless its rival cells are assessed, so the rival read comes before the row, in the same leg as the bars
2026-10-03	LP9	land	the document viewer alpha is live on the firm's domain at https://andelinwest.com/alpha/docs/ (fictional samples only, noindex, registered as draft rows in the site's publish plane): the first client-visible proof of the native format and the unified page. The stage is ALPHA; beta needs the law panel (unidoc UD10) and the Utah execution rows (LP23, LP30)
2026-10-03	LP9	measure	decision recorded with its evidence (which daemon carries the client document URL): the live vault daemon nx_docportal_admin_daemon already fronts andelinwest.com and serves /doc?cid= and /search, while nx_legal_portal_daemon is a loopback demo fixture around the lp_handle router. Recommendation: mount the document URL on the live daemon (unidoc UD3) and compose the legal portal routes as a library; do not deploy a second daemon. Still the operator's to confirm, together with delivery posture outside Utah, attorney sign-off per state (proposed yes) and opening portal.andelinwest.com
2026-10-03	LP9	measure	the firm's whole domain was unreachable in a browser from 2026-09-30 22:59 UTC to 2026-10-03 about 22:28 UTC: its certificate had expired and nothing alarmed (deploy board DL22 and DL26 carry the mechanism and the fix). A portal that holds wills cannot ride an edge whose certificates lapse in silence; DL26 to DL31 are a dependency of any beta
2026-10-07	LP30	land	2026-10-07 board hygiene: seven rungs (LP30 to LP36) had no matrix row and nx_compare_rank read them UNMAPPED; watch rows landed on legalpractice.matrix hosted on runtime/nx_law_core.nx (LP30, LP32, LP33, LP34), runtime/nx_tmplstale_lib.nx (LP31, LP36) and runtime/nx_legal_portal.nx (LP35), the dated bar SB-ESIGN (July 2026, attested by a 2026-10-07 read of the listing) with two targets and a role on every rung make the board LADDERED, and the rival census (ecosystem EC88) gets legalpractice.rivals (12 mirrored pages over four columns) and legalpractice.cellkeys (46 keyed cells from the pages' witnessed words)
2026-10-07	LP10	queue	rival census pass 1 on this board: adjudicate the proposals, refine the phrase table from the lesson rows and re-grade; the October 2026 DocuSign eSignature page carries no audit trail, identity verification, notary or eIDAS text (those live on the sibling pages mirrored in August), so column 1 cells for those rows are witnessed by the August mirrors until the sibling pages are re-read this month
2026-10-07	LP14	lesson	OPERATOR 2026-10-07: the office rivals (Google Docs, Word, Acrobat, Nextcloud) belong to the document compare (unidoc) and this board is specific to the practice (DocuSign, Clio, NetDocuments, PandaDoc); measured the same hour: eleven rows here duplicate unidoc rows (dad_handle, dx_to_html, nx_ann_add, nx_doc_serve_response, nx_env_send, odt_read_text, of_coedit, of_import, of_save, of_sign_version, pf_to_html) graded against a different rival set, and LP14 is unidoc UD8 under another id; the fix is the cross-board row kind on ecosystem EC89 (a row rendered from its home board and graded once); until it lands LP14, LP15 and LP22 carry unidoc:UD8, unidoc:UD13 and unidoc:UD25 as deps so the ranker reads the home rung's state, and the eleven rows stay graded here only against the practice rivals' own pages
2026-10-07	LP10	measure	rival census (nx_rivalcensus, ecosystem EC88) on this board, 2026-10-07: pass 1 over the 12 mirrored practice pages read 52 keyed cells, 23 exact, 12 presence (Yes proposed where the seat graded Best), 17 disagree, 442 permil exact and 673 with presence; pass 2 after four phrases were replaced by the pages' own words (document generation, sets of documents, collect signatures, questionnaires) and two silent cells were withdrawn to No by evidence (ODT on all four rivals, PDF on NetDocuments) read 32 exact, 12 presence, 8 disagree, 615 permil exact and 846 with presence, ratchet HOLDS; the 8 remaining lessons in legalpractice.census_lessons are three phrase gaps (Word on the NetDocuments pages, bulk send on the PandaDoc pages, template on the NetDocuments automation page) and five Parts the seat holds against a vendor mention (eIDAS through partners, DocuSign Notary off Utah's vendor list, PandaDoc payments against billing from trust, Clio legal AI); 228 of 280 cells are UNKEYED and are the next phrase pass, from the pages' witnessed words only
2026-10-08	LP14	land	2026-10-07 cross-board rows live (ecosystem EC89): five document rows that duplicated unidoc rows are now @xrow references to their home board (dx_to_html, odt_read_text, pf_to_html, of_save, nx_doc_serve_response), rendered on this page from unidoc's own cells under unidoc's columns and never re-graded here; the census partition reads xrows=5 and the position map, ranker and leaderboard count only this board's own rows; of_import (LP1), of_sign_version (LP4), of_coedit (LP14), dad_handle, nx_env_send and nx_ann_add stay as practice rows; the matrix landed on a predicted size ladder 36103 to 35762 to 35753 to 35758 to 35770 under CAS, every step byte-exact
2026-10-08	LP14	land	2026-10-07 second wave of cross-board references, chosen by the fleet duplicate census (nx_rivalcensus dupes, ecosystem EC89) rather than by hand: six more rows that graded a capability this board does not own became @xrow references to the home board that does: dx_emit_track, dx_cm_add, pf_check and of_llm_complete to /compare/office (the office suites are their rivals), dad_handle and the on-premise property row (its witness was docx_write, an office symbol) to /compare/unidoc; each reference keeps the practice reading in its note and names the practice-specific row that stays here (dx_html_track LP11, nx_ann_add, pf_defined_terms LP22, cl_review LP21, lp_handle and lpd_serve_realm LP9); landed on a predicted size ladder 35770 to 36036 in six steps, every receipt byte-exact; none of the six carried a rung, so the ranker stays at unmapped=0. Still duplicated and waiting on the ranker's reference-mapped rungs: of_import (LP1), of_sign_version (LP4) and of_coedit (LP14) against unidoc
2026-10-08	LP14	land	2026-10-07 the last two unidoc duplicates on this board became references once the ranker could carry a rung by reference (ecosystem EC89, nx_compare_rank 9caa9c3e): of_import (rung LP1, done) and of_coedit (rung LP14, open) are @xrow unidoc rows now, 36036 to 35913 to 35971 bytes under CAS; the ranker reads LP1 MAPPED-BY-REFERENCE state=DONE and LP14 MAPPED-BY-REFERENCE state=OPEN with unmapped=0 and xref_rows=13; LP14 is to be retired onto unidoc:UD8 through the lifecycle (UD8 already names the shared contract). This board now carries 13 references and grades 50 rows of its own; the fleet census reads no capability duplicated between legalpractice and unidoc
2026-10-08	LP14	retract	2026-10-07 LP14 RETIRED AS A CLAIM on this board (rungrole arm -> superseded, target T-BIC-ESIGN, successor unidoc:UD8): co-editing in the office is one capability and it is graded on /compare/unidoc (ecosystem EC89); this board keeps LP14 as the practice-side pointer, mapped by reference to unidoc's of_coedit row (the ranker reads RUNG LP14 MAPPED-BY-REFERENCE state=OPEN), and it closes the hour UD8 closes. Nothing is deleted: the rung row, its deps (LP3, unidoc:UD8) and every earlier log row stand; the ladder census now counts one superseded role here. The lifecycle (ecosystem EC71) owes the ranker a rung state that drops a superseded rung from the critical path instead of pricing it at its home deficit; until then LP14 ranks as its home row does, which is honest and visibly duplicated.
2026-10-08	LP1	land	2026-10-07 the last two document rows that were graded here against the practice rivals, docx_read_text and docx_read_spec (every practice rival Yes, no discrimination on this board), moved home to /compare/unidoc and became @xrow references here (35971 to 35903 to the next receipt under CAS); of the nine document rows named on 2026-10-07, five are now references to unidoc or office (dx_to_html, odt_read_text, pf_to_html, of_save, nx_doc_serve_response earlier; docx_read_text, docx_read_spec now), three are @xrow office (dx_emit_track, dx_cm_add, pf_check), and the four watch rows that remain practice rows carry this board's own rungs: of_inline_runs and dx_patch_para (the beyond-Google-Docs round trip, LP12 class), dx_html_track (LP11, the read side of redlines for review without Word) and pf_defined_terms (LP22, the Litera class of proofing, practice-specific by nature). The first two are candidates to move home once unidoc declares the editor rungs; queued, not moved, because moving a watch row moves its rung and that is unidoc's RACI lane.
2026-10-08	LP14	measure	2026-10-07 the ranker candidate that carries the superseded rung state (ecosystem EC71, nx_compare_rank 29770f3d, shipping) read this board in the ship probe: RUNG LP14 SUPERSEDED target=T-BIC-ESIGN state=OPEN deps=LP3,unidoc:UD8, summary rungs=35 done=7 open=27 superseded=1 (the promoted ranker read open=28 and ranked LP14 number 3 of the 1.0 critical path with priority 1400 beside a DARK-CONTRACT note); the retired claim is no longer ranked, no longer the third PM filing (LP11 takes that seat), no longer a cross-board edge (XDEP edges 7 to 6, the unidoc:UD8-blocks-LP14 row gone), and is persisted as a superseded row in legalpractice.rank. The board's own work is unchanged: LP9, LP10 and LP11 lead the 1.0 critical path in both runs.

On these two registers. Rows are declared in the domain's plan file and carry the debt id, which is the join key back to the sovereign debt plane — that plane, not this page, is the authority on state. Reconciling them automatically (the regen reading the plane and refreshing these rows) is a named, owed rung; until it lands, treat an id here as a pointer to look up, not a status to trust.

Honest verdict. The coverage above records source-symbol presence. Stronger comparisons are authored claims, not measured runtime superiority or accepted outcomes. A watch contract names an expected source symbol; finding it changes source discovery only. Qualification, deployment and runtime acceptance require their own evidence.

Person · product · place — not yet measured for this domain

Every compare carries this layer. Declare knowledge/compare/legalpractice.ppp (rows surface|nishi or c1..c4|label|url|connect naming OUR live surface and each rival's front door), run nx_ppp_probe domain legalpractice, and this section fills itself on the next beat: the same ruler on both sides — privacy and CX (third-party hosts, tracker classes, cookies, security headers), design and longevity (design hygiene, computed WCAG contrast, render-blocking resources, unsized media, script weight, theme and motion queries), findability (landmarks, skip link, on-site search, breadcrumb, headings, internal links).

The field — discovered, not chosen

Rows written by nx_field_discover from legalpractice.seeds: the industry's own lists (Wikipedia wikitext, GitHub topics, awesome lists) read mechanically, every candidate counted across seeds. The matrix columns above are a SEAT'S pick; this band is the population they were picked from, and the stats line measures one against the other. A rival here is a lead, never a verdict — it earns a column when its capabilities are read and pinned.

Discovery receipt. One row per counter the run wrote, in the receipt's own order; the rival rows follow in their own table.

Field discovery, counted
Class	Count	Note
seeds	4
scanned	4
fetched	4
reused	0
failed	0
named	4
candidates	4
mentions	4
capped	0

Rank	Rival	Seeds	Mentions	First seed	Kind	Link
1	DocuSign	1	1	col0-docusign	named	https://www.docusign.com/products/electronic-signature
2	Clio	1	1	col1-clio	named	https://www.clio.com/draft/
3	NetDocuments	1	1	col2-netdocuments	named	https://www.netdocuments.com/
4	PandaDoc	1	1	col3-pandadoc	named	https://www.pandadoc.com/electronic-signature-software/

Exclusive and shared capabilities

One capability is graded on one board; every other board references it. The fleet duplicate census (nx_rivalcensus dupes, on the fleetdupes clock row) reads every board's matrix and names each capability graded as a row on two or more boards, with a home derived from evidence: rung when exactly one board's plan contracts the symbol (that board is starred), gates when no plan contracts it and exactly one board's executed gate map runs the organ's gate (that board is plussed), ambiguous when several boards carry the deciding evidence (a decision for their seats), and none when no evidence decides it, with the reason beside it: unmapped (no board of the duplicate declares a gates map; declare the maps) or unproven (a map exists and runs none of the organ's gates; gate the organ on its proving board, or declare it a shared library by policy). A home elsewhere means this board should carry an @xrow reference to the home board's row rather than a graded row of its own; a home here means the other boards should. The table is this board's slice of one estate-wide census: the shape is shared, the rows are the board's.

This board grades 55 capabilities: 52 exclusive to it and 3 shared with other boards. Shared rows on this page: 3 = home here 0 + home elsewhere 1 + ambiguous 0 + undecided 2 + refused 0 (partition 3); undecided = unmapped 0 + unproven 2 + unevidenced 0; homonyms 0; since the previous census: new 0, resolved 0. Census FRESH age_s=6673.

Capability	Organ	Boards grading it	Home	Rule	Evidence	Standing on this board
trust_disburse_ok	`nx_trust_lib.nx`	finance, legalpractice, appliedmath	—	none	unproven	undecided
se_chain	`nx_sign_envelope_lib.nx`	legalpractice, modding+	modding	gates	gates	home elsewhere adopt: `@xrow modding\|se_chain\|home by gates (fleet duplicate census)`
bl_bill_from_trust	`nx_billing_lib.nx`	legalpractice, appliedmath	—	none	unproven	undecided

Gaps from the record — what the estate does that no board carries

The record census (nx_goalmap record) reads the invoked-tool population and every plan queue row and files each organ or directive that NO matrix, plan or gates row names. A row here is a callout the boards missed: adjudicate it onto a board or declare it infrastructure. Census state STALE (age 1395778 s), sources read 4 of 7 declared — a BLIND census is a FLOOR: unread sources can only add rows.

kind	name	board	source	evidence
directive	`nx_unidoc`	legalpractice	plan-queue	rung=LP9

rows shown 1|this board's directives 1|estate-wide un-boarded organs 452 (listed in full on /compare/ecosystem)|census rows 639|malformed 0 (counted, never rendered)

References

Beyond a link list. Every reference below resolves twice — the publisher's copy and, where banked, the estate's own non-rottable library mirror with a content pin — and carries its evidence class plus the exact claim on this page it grounds. Keyed marks like [key] in the matrix notes jump here. A dash means honestly absent, never assumed.

[docusign-esign] Docusign. Electronic Signature -- Fast and Easy e-Signature (product page): send and sign agreements, templates, bulk-send envelopes to multiple signers, digital certificates and audit trail kept on the Docusign service. Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_legalpractice_docusign-esign.html · pin hb75fb3cb270ab6cfa624b63c92caa1776cdd82636a04f5924f24341ceb05fabe · accessed 2026-08-18 · vendor-docGrounds: The DocuSign column: Yes on the SIGN audit, ceremony, certificate and routing rows (vendor-hosted audit trail is why our hash-chain row grades an exceed), Yes on 'Bulk send' (the page lists bulk-send envelopes to multiple signers), Yes on 'Contract lifecycle' (agreement dates across the IAM platform).
[docusign-idv] Docusign. Docusign Identify -- identity verification for signers (ID document verification, knowledge-based and phone authentication) (product page). Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_legalpractice_docusign-idv.html · pin h5be07bc66fb5adb1590ec2d50589bb9f87d68b43e9ca1445f1b37509bdd61bfa · accessed 2026-08-18 · vendor-docGrounds: The DocuSign Best code on 'Signer identity verification ladder': the reference the sc_signer_idv watch is measured against.
[docusign-notary] Docusign. Docusign Notary -- remote online notarization on the Docusign platform (product page). Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_legalpractice_docusign-notary.html · pin h64b3ad7d2c4f3a2b52e3c247d0d98d3539e9b873d379e7b76022a7c482d48aca · accessed 2026-08-18 · vendor-docGrounds: The DocuSign Part code on 'Remote online notarization': the product exists, and the Utah Lieutenant Governor's approved-vendor list does not carry it, so it grades Part for a Utah practice.
[docusign-docgen] Docusign. Document Generation -- generate agreements from templates and data (product page). Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_legalpractice_docusign-docgen.html · pin he44af5db9e124ef93b38f1788df07689867e931a574de8914256ed9beca02f77 · accessed 2026-08-18 · vendor-docGrounds: The DocuSign Yes on 'Clause library and templates', 'Field merge' and 'Template registry': template-driven generation is documented here; downstream lineage and staleness are not, which is why the CLERK rows read 0.
[clio-draft] Clio. Clio Draft -- AI legal document automation: convert existing Word files into reusable templates, up-to-date fillable court forms for all 50 states, AI-powered client questionnaires, populate whole document sets, collect e-signatures (product page). Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_legalpractice_clio-draft.html · pin h2228cbe3e322b2ea043d4dd5981ece5e776dc8def18a1510ff1040af7121f6fd · accessed 2026-08-18 · vendor-docGrounds: The Clio column on the ASSEMBLE rows and its Best on 'Court forms refresh' (always-current fillable court forms), Yes on 'New-matter intake' (questionnaires), Part on the tracked-revision rows because Draft hands the file to Word.
[clio-portal] Clio. Legal Client Portal With AI for Law Firms -- Clio for Clients: secure document sharing, messaging, e-signature and payments in one client portal (product page). Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_legalpractice_clio-portal.html · pin h261e8d6160b44409f3deda0c0001a09895dce12f399e0d3463045d5e0edb15ae · accessed 2026-08-18 · vendor-docGrounds: The Clio Best code on the PORTAL vault, workspace and served-portal rows and Yes on 'Secure client messaging': the portal reference the andelinwest.com rungs are measured against.
[clio-features] Clio. Clio Manage features -- calendaring, case and task management, legal documents, accounting, billing, online payments, time and expense tracking, trust account management, client portal, workflow automation and legal AI (features index). Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_legalpractice_clio-features.html · pin h3ff3668b3952e38ec5a4e989e0207d952f93e61cdaebb75bc8b3f3244320c314 · accessed 2026-08-18 · vendor-docGrounds: The Clio Best codes on 'Time and billing' and 'Trust accounting IOLTA' and its Yes on 'URCP docketing' (calendaring); the conflicts row grades Clio Part because this index does not name conflict search.
[netdocuments] NetDocuments. Document and Email Management for Legal Firms and Departments (home page): cloud DMS with matter-centric workspaces, Word integration and legal AI. Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_legalpractice_netdocuments.html · pin hbdd6254a2e58323a4f4ecf0b5dc33c7c1e37ff702fd643c33e1d1f45dc0d740b · accessed 2026-08-18 · vendor-docGrounds: The NetDocuments Best code on 'Matter-scoped DMS' (the legal DMS reference), Yes on the version-history and co-editing rows (through Word), Part on the SIGN rows (signing through integrations).
[netdocs-docauto] NetDocuments. Legal Document Automation and Assembly Software (solutions page): template-driven assembly inside the DMS. Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_legalpractice_netdocs-docauto.html · pin hf05e49d7f90dcf2be599293aa6a456af8083562a7440ac219056bdde99440e3c · accessed 2026-08-18 · vendor-docGrounds: The NetDocuments Yes on 'Clause library and templates', 'Field merge', 'Mail merge' and 'Template registry'.
[pandadoc-esign] PandaDoc. Electronic Signature Software (product page): legally binding e-signatures under ESIGN, UETA and eIDAS, a digital certificate and a full audit trail (who opened, viewed and signed, timestamps, IP addresses), templates and bulk send. Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_legalpractice_pandadoc-esign.html · pin heb857f08debd12a37edb8fb7e98411d5716fedbf4f370369a95079d9b0d6b164 · accessed 2026-08-18 · vendor-docGrounds: The PandaDoc column on the SIGN rows (Yes on audit, ceremony, certificate, routing, bulk send; Best on field placement) -- its audit trail is kept on the PandaDoc service, the contrast our hash-chain exceed names.
[pandadoc-templates] PandaDoc. Templates -- reusable document templates and content library (product page). Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_legalpractice_pandadoc-templates.html · pin h362a8fcc2023618ca1b84819de8af36a5c5e256952d639dde8dd38a208595d94 · accessed 2026-08-18 · vendor-docGrounds: The PandaDoc Yes on 'Clause library and templates' and 'Template registry'.
[esign-15usc7001] 15 U.S.C. section 7001 -- General rule of validity (Electronic Signatures in Global and National Commerce Act, ESIGN), including the 7001(c) consumer-consent conditions. Legal Information Institute, Cornell Law School. publisher · read in our library knowledge/fetched/cmp_legal_esign-15usc7001.html · pin h975a5f762bc64f153f2f396cfc0600f50366a406383aefc1b56420cf020013c1 · accessed 2026-08-18 · published-standardGrounds: The 'UETA and ESIGN consent-gated ceremony' and 'Legal-validity verdict per signature' rows: the federal validity rule and the consumer-consent overlay that es_esign_valid and es_consumer_ok compute per signature.
[esign-7003] 15 U.S.C. section 7003 -- Specific exceptions to ESIGN: laws governing the creation and execution of wills, codicils or testamentary trusts, family law, most of the UCC, court orders and notices. Legal Information Institute, Cornell Law School. publisher · read in our library knowledge/fetched/cmp_legalpractice_esign-7003.html · pin he2628f8d9a56507bc2daae1945763090db94bc53b9f26e673713642318fff581 · accessed 2026-08-18 · published-standardGrounds: The 'Never-void instrument gate' row: the federal carve-out that makes a Will routed for ordinary e-signature a void execution, which nx_legal_regime refuses at send and at seal.
[utah-ueta-201] Utah Code 46-4-201 -- Legal recognition of electronic records, electronic signatures and electronic contracts (Utah Uniform Electronic Transactions Act, Title 46 Chapter 4). Utah State Legislature. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-ueta-201.html · pin hfd5c071fa99de4ace7d41de850e2722c7956a7fbf00eced57c8565bd39da4165 · accessed 2026-08-18 · published-standardGrounds: The 'UETA and ESIGN consent-gated ceremony' row: Utah's enactment that a record or signature may not be denied legal effect solely because it is electronic; 46-4-103 in the same chapter carves out wills, grounding the never-void row.
[utah-ewill-1405] Utah Code 75-2-1405 -- Execution of an electronic will (Uniform Electronic Wills Act, effective 2020-08-31): a record readable as text, signed by the testator, and signed by at least two witnesses in the physical or electronic presence of the testator. Utah State Legislature. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-ewill-1405.html · pin hb22a204187b0bf1c4b1f8be60bac75691acd6d372ab35b061181d235785aa774 · accessed 2026-08-18 · published-standardGrounds: The 'Never-void instrument gate' row: Utah is an e-wills state, so the gate must let a compliant electronic will route (two witnesses, electronic presence allowed) while refusing the unwitnessed one.
[utah-ron-46-1-3-6] Utah Code 46-1-3.6 -- Remote notarization procedures (effective 2026-05-06, amended by Chapter 56, 2026 General Session): remote notary physically in Utah, simultaneous sight-and-sound communication plus an identification image, an electronic recording of each remote notarization, and satisfaction of personal-appearance requirements. Utah State Legislature. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-ron-46-1-3-6.html · pin h48383c64eeeb5c1e74b6841bff7fe878e04bf0a630322466ce82d5a128122faf · accessed 2026-08-18 · published-standardGrounds: The 'Remote online notarization' row: the elements the ron_session watch must record (Utah-located notary, A/V, ID image, recording), current as of the 2026 amendment.
[utah-r623-100-9] Utah Administrative Code R623-100-9 -- Remote Notarization: Recording; the solution provider must generate a printable version of all documents and associated tamper-evident certifications, and the certificate must state the principal appeared remotely by audio-video technology. Legal Information Institute mirror of the Utah rule. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-r623-100-9.html · pin haf68f191512d5fe0988db9f1bfa998facb424d0d7aa4616c4a5f6efa2373b087 · accessed 2026-08-18 · published-standardGrounds: The 'Remote online notarization' row: the provider-side output contract (tamper-evident certifications, remote-appearance certificate wording) that a sovereign RON record must satisfy.
[utah-ron-vendors] Utah Lieutenant Governor, Notary Office. Approved Remote Notary Vendors (list, last verified 2025-11-18): the platforms a Utah remote notary may use, each shown Active, including PandaDoc; Docusign is not listed. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-ron-vendors.html · pin h11841d8d851b04cca0afe3bd56b3e0de54ba97127eceffaa212bdf4e9fcf98d4 · accessed 2026-08-18 · vendor-docGrounds: The 'Remote online notarization' row: PandaDoc Yes and Docusign Part are read from this state list, not from the vendors' own pages.
[utah-rpc-1-15] Utah Supreme Court Rules of Professional Practice, Rule 3-1.15 (previously UCJA 13-1.15) -- Safekeeping Property: client funds in a separate trust account, complete records preserved for five years after the representation ends, own funds only for bank charges, advance fees withdrawn as earned. Utah State Courts. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-rpc-1-15.html · pin h98f516fa237120410db64a7186e753f82c3c8f2296b11c7546678f5cf98739c6 · accessed 2026-08-18 · published-standardGrounds: The 'Trust accounting IOLTA' and 'Time and billing' rows: the Utah rule text nx_trust_lib and nx_billing_lib enforce (no commingling, no overdraw, records kept).
[utah-iolta-4-1001] Utah Supreme Court Rules of Professional Practice, Rule 4-1001 -- Interest on Lawyers Trust Accounts (IOLTA), effective 2025-07-09 (formerly UCJA 14-1001): interest-bearing trust account for nominal or short-term client funds, earnings remitted to the Utah Bar Foundation, annual certification. Utah State Courts. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-iolta-4-1001.html · pin hb0993d8499786554992f00ca1bc1bc7a7aeb39c339dd84bb37deb0292d9e0f2c · accessed 2026-08-18 · published-standardGrounds: The 'Trust accounting IOLTA' row: the current Utah IOLTA rule the trust ledger is measured against.
[utah-efiling] Utah State Courts. District Court e-Filing for attorneys: attorneys may build a system to submit electronic filings; a non-disclosure agreement is required of all Electronic Filing Service Providers and filers building an interface, after which an eFiling Integration Guide describing the API is provided. Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-efiling-district.html · pin hc898ee22c1cfa74a5b040ffedcbcaefc9e0998b0956c6ada0299579d88e805e2 · accessed 2026-08-18 · published-standardGrounds: The 'Utah e-filing connector' row: the connector is buildable by a filer under NDA, so the efl_submit watch is a lane with a named unblock, not a guess.
[aba-rule-1-7] American Bar Association. Model Rules of Professional Conduct, Rule 1.7: Conflict of Interest -- Current Clients. publisher · read in our library knowledge/fetched/cmp_legal_aba-rule-1-7.html · pin hc00ea96f94678376a0bc513bc61b3a3eec3773e2ca87b02a37c3f7cdb891cf07 · accessed 2026-08-18 · published-standardGrounds: The 'Matter spine plus RPC 1.7 and 1.9 conflicts check' row: the current-client conflict rule mt_conflict implements.
[aba-rule-1-15] American Bar Association. Model Rules of Professional Conduct, Rule 1.15: Safekeeping Property. publisher · read in our library knowledge/fetched/cmp_legal_aba-rule-1-15.html · pin h1467a6a1dccf7c4d2ecf6fad846d35790671605acea29511e26373a46373a3ea · accessed 2026-08-18 · published-standardGrounds: The 'Trust accounting IOLTA' row: the model rule behind Utah 3-1.15.
[ecma-376] Ecma International. ECMA-376: Office Open XML File Formats (WordprocessingML, Open Packaging Conventions), also ISO/IEC 29500. publisher · read in our library knowledge/fetched/cmp_office_ecma376.html · pin h7861648cf663c18dbdc3a4d4779b8de50603ec0604b1a3ee6d571ea76efe84f7 · accessed 2026-08-18 · published-standardGrounds: The OPEN and EDIT rows on .docx read, tracked revisions (w:ins, w:del), comments and the MERGEFIELD watch: the package and elements our own reader and writer implement.
[odf-1-3] OASIS. Open Document Format for Office Applications (OpenDocument) Version 1.3, Part 1. OASIS Standard, 2021 (also ISO/IEC 26300). publisher · read in our library knowledge/fetched/cmp_office_odf13.html · pin hdbfa9338c0751bcc8248a77aa421ab00ef0cad1fd237ed445a3469fecafae330 · accessed 2026-08-18 · published-standardGrounds: The 'OpenDocument .odt read and write' row.
[ms-word-mailmerge] Microsoft. Word VBA reference -- MailMerge object (Microsoft Learn): the mail merge model behind Word merge fields and data sources. Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_legalpractice_ms-word-mailmerge.html · pin hb21f46b9abb4863d9e72ea756a7455e3df5407d7b967e5152409f138f13790b3 · accessed 2026-08-18 · vendor-docGrounds: The 'Mail merge' and 'Word MERGEFIELD field codes' rows: the incumbent merge model a lawyer's existing templates were authored against, and the reason the double-brace merge is graded present while the field-code watch stays open.
[vals-vlair] Vals AI. Vals Legal AI Report (VLAIR): CoCounsel, Vincent AI, Harvey Assistant and Oliver measured against a lawyer baseline on document Q and A, extraction, summarization, redlining, transcript analysis and chronology; on redlining the lawyers scored 79.7 percent against 59.4 (Harvey) and 53.6 (Vincent). Accessed 2026-08-18. publisher · read in our library knowledge/fetched/cmp_legalpractice_vals-vlair.html · pin h21714fd53458c08192ea35cb8b1a86b194205d6166fde459b1052f5f49d4b118 · accessed 2026-08-18 · published-paperGrounds: The 'Contract review grounded on the clause library' row: the independent benchmark showing AI redlining below the lawyer baseline, the reason the cl_review watch is designed as clause-grounded cite-or-abstain rather than free generation.
[magesh2024] Magesh, Surani, Dahl, Suzgun, Manning, Ho. Hallucination-Free? Assessing the Reliability of Leading AI Legal Research Tools. arXiv:2405.20362, 2024 (Stanford RegLab / HAI). publisher · read in our library knowledge/fetched/cmp_legal_magesh2024.html · pin hf724e03a034bb9f1b3a099f1782fd1219d67a3eb9c7cd721a7de8ac97f6c66f0 · accessed 2026-08-18 · published-paperGrounds: The 'Contract review grounded on the clause library' row: the published measurement of unsupported citations in legal AI answers.
[nist-800-63a-4] NIST. Special Publication 800-63A-4, Digital Identity Guidelines: Identity Proofing and Enrollment (final, July 2025): identity assurance levels, evidence strength, document validation, remote and on-site proofing, presentation-attack detection. publisher · read in our library knowledge/fetched/cmp_legalpractice_nist-800-63a-4.html · pin hf60296577b7ce92458f1109718d86684361858b6a858bac06b83ea07814cefbb · accessed 2026-08-18 · published-standardGrounds: The 'Signer identity verification ladder' row: the bar the government-ID leg of sc_signer_idv is measured against.
[aba-op-512] American Bar Association, Standing Committee on Ethics and Professional Responsibility. Formal Opinion 512: Generative Artificial Intelligence Tools (July 29, 2024) -- competence, confidentiality (informed consent before client information enters a self-learning tool), communication, candor, supervision and fees. The publisher returned HTTP 403 to the sovereign fetcher on 2026-08-18, so no mirror is banked; the URL was witnessed. publisher · accessed 2026-08-18 · published-standardGrounds: The 'On-premise, no telemetry' row: the ethics duty that makes on-host processing of client documents a stated property of the stack rather than a marketing line.
[utah-hb181-ueepda] Utah H.B. 181 (2026 General Session), Uniform Electronic Estate Planning Documents Act, enrolled copy, effective 2026-05-06, enacting Utah Code 75-13-101 through 75-13-303: a non-testamentary estate planning document (a trust instrument, a trust power, a durable power of attorney, an advance health care directive, a guardian nomination, a disclaimer and more, never a will and never a deed or a vehicle, watercraft or aircraft title) may be signed electronically; a required notarization, acknowledgment, verification or oath is satisfied when the authorized individual attaches or logically associates an electronic signature with the other required information (75-13-206); a signing, witnessing or attestation presence requirement is satisfied in electronic presence, defined as communicating in real time to the same extent as if physically present (75-13-207); an electronic record satisfies an original-form rule (75-13-208); a certified paper copy is made by affirmation under penalty of perjury (75-13-209); applies to documents created before, on or after 2026-05-06. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-hb181-ueepda.pdf · pin h519d5adf62ca37083e55f56c8a46befc108ca861acf1278ec42a2dce6e42a868 · accessed 2026-09-03 · published-standardGrounds: The 'Execution ladder keyed by instrument and Utah statute', 'Remote witnessing session' and 'Certified paper copy' rows: the 2026 regime for every estate instrument that is not a will.
[utah-sb139-notary-2026] Utah S.B. 139 (2026 General Session), Notary Amendments, enrolled copy, effective 2026-05-06: satisfactory evidence of identity for a remote notarization is an unexpired government photo identification or passport PLUS secondary authentication by a third party through dynamic knowledge-based authentication or biometric analysis (46-1-2(25) and (26)); a remote notary keeps a secure electronic journal; the journal and each electronic recording of a remote notarization are retained for 10 years; attorneys, law firms and title agencies are exempt from certain journal requirements. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-sb139-notary-2026.pdf · pin h29e9c82dcdc17b131c798b8669e6abb59b9bf4a88d69382d16b32410bbf0ce92 · accessed 2026-09-03 · published-standardGrounds: The 'Remote online notarization' row (identity and retention elements current as of the 2026 amendment) and the retention terms of the 'Living estate vault' row.
[utah-sb275-sedi] Utah S.B. 275 (2026 General Session), State-Endorsed Digital Identity Program Amendments, enrolled copy, effective 2026-05-06, enacting Utah Code Title 63A Chapter 20: a digital identity bill of rights (the right to use a physical identity instead, the right to be free from surveillance, profiling or tracking through presentations), selective disclosure of identity attributes, open technological standards, a digital guardian who may obtain and present the identity for a minor or incapacitated individual, verifier and relying-party duties to process only the minimum attributes reasonably necessary and to accept a digital guardian's presentation, no surrender of the holder's device; the electronic license certificate statute (63A-16-1201 to 1203) is repealed on 2027-01-01. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-sb275-sedi.pdf · pin hb79f9f11392aecee0a5c3bce87da762773932c706cc2352b0e38b1fd971f4301 · accessed 2026-09-03 · published-standardGrounds: The 'Signer identity through Utah SEDI' row and the digital-guardian path of the 'Living estate vault' row.
[utah-sedi-guide] Utah Department of Government Operations, State-Endorsed Digital Identity (SEDI) Implementation Guide (web), the program's published guidance for wallets, verifiers and relying parties under Title 63A Chapter 20. Accessed 2026-09-03. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-sedi-guide.html · pin h831231ef08e607f176f187ca6bf30713afb03323bd45ffe7a9934012cab62f70 · accessed 2026-09-03 · published-standardGrounds: The 'Signer identity through Utah SEDI' row: the relying-party posture the sc_idv_sedi watch is measured against.
[utah-r623-100-5] Utah Administrative Code R623-100-5, Remote Notarization: Credential Analysis and Authentication -- credential analysis by a reputable third-party vendor or software tool with an authenticity test of the identification's visual, physical or cryptographic security features and a check against the issuing source, the principal's identity bound after knowledge-based authentication or biometric data, and a human visual comparison between the principal and the presented identification. Legal Information Institute mirror of the Utah rule. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-r623-100-5.html · pin h0760e362b061a71c749f36f12d445087cb7d71b64d12377283166edc3dbfb55f · accessed 2026-09-03 · published-standardGrounds: The 'Remote online notarization' row: the provider-side identity contract a sovereign RON record must satisfy.
[utah-ewill-1408] Utah Code 75-2-1408 -- Electronic will attested and made self-proving at time of execution (effective 2020-08-31): the testator's acknowledgment and the witnesses' affidavits are made before an officer authorized to administer oaths and evidenced by the officer's certificate under official seal affixed to or logically associated with the electronic will; the statutory affidavit form recites the witnesses' physical or electronic presence; a signature physically or electronically affixed to the affidavit is deemed a signature of the will; the section supersedes the Notaries Public Reform Act where they conflict. Utah State Legislature. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-ewill-1408.html · pin h1607340d5f2f6ca1083d360422f001e2b93c176a580b82db97f27c2f43421032 · accessed 2026-09-03 · published-standardGrounds: The 'Execution ladder keyed by instrument and Utah statute' row: the self-proving element of an electronic will.
[nist-800-63b-4] NIST. Special Publication 800-63B-4, Digital Identity Guidelines: Authentication and Authenticator Management (final, July 2025): authenticator assurance levels, phishing-resistant authentication, syncable passkeys and multi-factor cryptographic authenticators. publisher · read in our library knowledge/fetched/cmp_legalpractice_nist-800-63b-4.html · pin h717c85f1fa8652ebf83ebfbd59290ef813ab1bcfe1256810eef6436bbd68cb5e · accessed 2026-09-03 · published-standardGrounds: The 'Passkey login with family-quorum and succession recovery' row: the AAL2 bar the browser passkey leg is measured against.
[chrome-dc-api] Google, Chrome for Developers. Digital Credentials API: secure and private identity on the web (blog, the API shipped in stable Chrome supporting OpenID4VP and ISO/IEC 18013-7 Annex C presentation from a wallet through the browser). Accessed 2026-09-03. publisher · read in our library knowledge/fetched/cmp_legalpractice_chrome-dc-api.html · pin h90ea795d277c3658130c841be1c65ea35b74575feedca4d5091a4a696e31a1bf · accessed 2026-09-03 · vendor-docGrounds: The 'Signer identity through Utah SEDI' row: the browser surface on Android and desktop Chrome that carries a wallet presentation to the signing page.
[webkit-dc-api] Apple, WebKit blog. Online Identity Verification with the Digital Credentials API (Safari 26 support for org-iso-mdoc presentation through the browser). Accessed 2026-09-03. publisher · read in our library knowledge/fetched/cmp_legalpractice_webkit-dc-api.html · pin hcc4e594887f89df31b721a364ccb2e17533a7f9ddb2c34c2571b4d369b4642d4 · accessed 2026-09-03 · vendor-docGrounds: The 'Signer identity through Utah SEDI' row: the iPhone surface for the same presentation.
[etsi-en-319-142-1] ETSI EN 319 142-1 V1.2.1 (2024-01), Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures (levels B-B, B-T, B-LT and B-LTA over ISO 32000). publisher · read in our library knowledge/fetched/cmp_legalpractice_etsi-en-319-142-1.pdf · pin h93e01407673ae22bdd0fadfc3a85df76411f1cfb1a3b53db47326a9d9658efb3 · accessed 2026-09-03 · published-standardGrounds: The 'Signed PDF output with an embedded PAdES signature' row: the baseline profile the pdf_sign_pades watch is measured against.
[wcag22] W3C. Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation, 2023-10-05: level AA success criteria including Target Size (Minimum) 24 by 24 CSS pixels, Dragging Movements, Focus Not Obscured (Minimum), Consistent Help, Redundant Entry and Accessible Authentication (Minimum). publisher · read in our library knowledge/fetched/cmp_legalpractice_wcag22.html · pin h6e3c5fe397257cae509a2fb4752b73062cf8cbeb92c2cec618989b17e4cf7057 · accessed 2026-09-03 · published-standardGrounds: The 'Mobile-first signing and review surface' row: the accessibility bar an elderly client's phone ceremony is measured against.
[natlawreview-ueepda] National Law Review. Utah Enacts Uniform Electronic Estate Planning Documents Act, Closing Gap in Digital Estate Planning Law (2026): effective 2026-05-06, trusts, powers of attorney and advance health care directives may be executed and notarized electronically, deeds and vehicle titles excluded, building on the 2020 Uniform Electronic Wills Act. Accessed 2026-09-03. publisher · read in our library knowledge/fetched/cmp_legalpractice_natlawreview-ueepda.html · pin hcec0c2ab82cc9ea61f41c38b0cd13caec002ec36d0ae72c8fb00f9df29c83275 · accessed 2026-09-03 · published-paperGrounds: The H.B. 181 bar on the plan: the secondary source that first flagged the enactment; the statute row above is the authority.
[utah-olsi-sandbox] Utah Office of Legal Services Innovation. The Sandbox (web): the Utah Supreme Court's regulatory sandbox for nontraditional legal services including technology-based providers, in Phase 3 and authorized to August 2027, with end-of-life planning among the areas served. Accessed 2026-09-03. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-olsi-sandbox.html · pin hab32b0e7546013d57353ba5fb05eb67d75d41e570ec0002494b4f4767e7c77bc · accessed 2026-09-03 · published-standardGrounds: The sandbox bar on the plan: the delivery posture under which a software-delivered estate service may operate in Utah.
[utah-eaoc-23-01] Utah State Bar, Ethics Advisory Opinion Committee. Opinion 23-01 (2023-08-10): a lawyer may ethically provide to the beneficiaries or heirs of a now-deceased client the estate planning documents the lawyer prepared, impliedly authorized under Rules 1.6 and 1.9 where the trustee or personal representative has not done so, grounded in the trustee's duty under Utah Code 75-7-811 to inform qualified beneficiaries within 60 days and furnish the trust instrument on request; work product only where it promotes the client's estate plan. publisher · read in our library knowledge/fetched/cmp_legalpractice_utah-eaoc-23-01.pdf · pin h8c3bf61b0e3904dddc1936d1aae9416bd58177e6f861525f25a0245a93c826c6 · accessed 2026-09-03 · published-standardGrounds: The 'Living estate vault' row: the ethics ground for a fiduciary release rule after death.
[secure-notarization-s1561] United States Congress. S.1561, SECURE Notarization Act of 2025 (119th Congress): a federal minimum standard and interstate recognition for electronic and remote notarizations, in committee as of September 2026. The publisher returned HTTP 403 to the sovereign fetcher on 2026-09-03, so no mirror is banked; the URL was witnessed. publisher · accessed 2026-09-03 · published-standardGrounds: The 'Remote online notarization' row: the national bar that has not yet passed, so the Utah statute remains the rule the ron_session watch implements.
[arxiv-esign-oct] arXiv API listing, search abs:"electronic signature" sorted by submission date, 15 entries read 2026-10-07. The phrase is a homonym: 12 of the 15 are condensed-matter and astrophysics papers using electronic signature in the spectroscopic sense (a Raman platform, ferromagnetism, X-ray absorption and the like); the 3 on-subject entries are arXiv 2607.09370 SFDS, Selective File Disclosure System (published 2026-07-10), arXiv 2601.19837v2 Self-Sovereign Identity and eIDAS 2.0: Control, Privacy and Legal Implications (revised 2026-03-05) and arXiv 2601.06554 QES-Backed Virtual FIDO2 Authenticators (published 2026-01-27). No October 2026 on-subject entry. publisher · read in our library knowledge/fetched/rf_17598d08.raw · pin ha6d035b458571b66781a7f7ca491f31d79a72a1a3420076643c60cc5c980cc3c · accessed 2026-10-07 · mirrored-indexGrounds: The dated bar SB-ESIGN: the research listing for e-signature, with its homonym partition named.
[docusign-esign-oct] Docusign. eSignature product page, read 2026-10-07: send, sign and manage agreements; templates (6 mentions), bulk send, routing, document generation, mobile signing (16 mentions) and the API; the words audit trail, identity verification, notary and eIDAS do not appear in the served text (they live on the sibling product pages mirrored in August), so this page witnesses the agreement-workflow surface only. Accessed 2026-10-07. publisher · read in our library knowledge/fetched/rf_fcefce85.raw · pin hc0b60bcdd44637ae992a3a8fb470c0cfce411e89b23ab4b5f4ccee5df6fab1fc · accessed 2026-10-07 · vendor-docGrounds: rival column 1 (DocuSign) current-month witness for the SB-ESIGN bar and the rival census

generated by nx_swcompare_matrix (sovereign NishiLang organ) from knowledge/compare/legalpractice.matrix · source checks show implementation presence; runtime and user-outcome evidence are reported separately · JavaScript supports page controls