⚠ Trunk Conflict — Genesis Already Exists
This node already has a genesis document anchored to the record. A second genesis cannot be submitted —
the trunk of this tree is sealed. To add to the record, select a different document type and link it
to an existing document using the parent picker below. The next logical document types are
amendment (a depth-1 extension of the genesis) or notice (a new branch at depth 1).
01 — Document Identity
Required for response documents — identifies the party entering the record.
Declaration Details
Jurisdiction and scope define where this declaration operates and how it branches in the tree.
02 — Named Parties
Separate multiple parties with a semicolon. Include full names as they appear on the instrument.
Court case number, county record number, or other external reference that anchors this document to a physical record.
Format: dosd:[interest]@[node-domain]![record-id]
The [interest] code belongs to the record, not the node.
The ! separates the node from the record.
Use the full URN to reference a record on any DOSD node federation-wide.
03 — Link to Parent Document
⚠ Parent document required. Root-level records are created and maintained by the site steward and are locked.
All submissions must attach to an existing anchored document. Search below to find the correct parent,
then complete your submission.
Parent Document *
Search the record to find the document this one extends, responds to, or evidences.
Search title, parties, description
Exact Document ID
SHA-256 hash (full or first 8+ chars)
Party name (partial match)
From date
To date
Document type
Record Reference Number (partial match)
Parent Document Selected
Doc ID
Type
Date
Parties
Chain depthparent is depth
→ this doc will be depth
SHA-256
Record Link—
⚖ Disclaimer — Document Custody
This form submits a record to the DOSD communication and standing record system only.
The submitting party is solely responsible for the safe-keeping of the original document.
DOSD does not store, guarantee, or bear custody of original instruments.
The SHA-256 hash anchored to the chain serves as cryptographic proof that the document
existed in its current form at the time of submission — the original must be preserved
by the submitting party to support that proof.
04 — Document & Hash
Document will be stored on the node. SHA-256 hash computed automatically and anchored to the chain.
📄
Click or drag a file here
PDF, PNG or JPEG image, or plain text — max 20 MB
Hash will be computed from your uploaded file and anchored to the chain.
Note —
The steward of this node can see all documents regardless of visibility setting.
CR + Parties visibility is only granted to a conflict resolution provider after their
attachment has been accepted by the parties — a CR provider cannot attach to view
private documents without party acceptance.
05 — Submission Fee
Select your payment method, send the fee to the handle shown, then enter your payment reference below.
No payment handles are set on this node yet — contact the steward for fee arrangements.
If you have a steward token, payment reference is not required.
⚖ Disclaimer — Perjury & Majority
By submitting this document, you declare, under penalty of perjury, that the information provided
is true and correct, and that this submission is made voluntarily and of your own free will,
without coercion or duress.
Majority status of the submitter is not affirmed or verified by this form. If you are under the
age of majority, you — the living man or woman submitting this record — are responsible for
notifying your parent or legal guardian and seeking their permission before this record is made.