Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Wire operations

The closed operation set: 63 operations. The wire name is each op’s serde identifier; its request and response payload schemas live under contracts/dli-worker/schemas/. Summary is Op::summary() — the same tool-selection text an agent reads over MCP. The batch dli.* family and the author.* authoring-seam tools are one closed set.

#Wire nameSummaryRequest schemaResponse schema
1dli.versionReport the worker contract version and this build’s wired capabilities.dli.version.request.jsondli.version.response.json
2dli.checkValidate a loaded document: self-consistency findings over the compiled world.dli.check.request.jsondli.check.response.json
3dli.queryQuery a saturated world for a goal atom’s support, grade, and standing.dli.query.request.jsondli.query.response.json
4dli.fork.newOpen a fork: an exploratory condition context over an unchanged world.dli.fork.new.request.jsondli.fork.new.response.json
5dli.fork.listList the open forks over a document.dli.fork.list.request.jsondli.fork.list.response.json
6dli.fork.diffShow a fork’s derived-consequence diff against the base ledger.dli.fork.diff.request.jsondli.fork.diff.response.json
7dli.fork.supposeAssume an option or event true within a fork and see what its consequences become.dli.fork.suppose.request.jsondli.fork.suppose.response.json
8dli.fork.addAdd proposed declarations into a fork — fork-local exploration, never canon.dli.fork.add.request.jsondli.fork.add.response.json
9dli.fork.suppressRetract an assumption from a fork.dli.fork.suppress.request.jsondli.fork.suppress.response.json
10dli.fork.restrictRestrict a fork’s valuation scope to a set of atoms.dli.fork.restrict.request.jsondli.fork.restrict.response.json
11dli.fork.preflightRatification pre-flight: the candidate valuation a fork implies and the conflicts it would introduce.dli.fork.preflight.request.jsondli.fork.preflight.response.json
12dli.fork.promoteEmit a ruling-request draft from a fork — the machine proposes, it never rules.dli.fork.promote.request.jsondli.fork.promote.response.json
13dli.check-proofCheck a diegetic proof block declared in a practice.dli.check-proof.request.jsondli.check-proof.response.json
14dli.timeline.showShow the timeline at a position.dli.timeline.show.request.jsondli.timeline.show.response.json
15dli.timeline.orderReport the partial order over the timeline.dli.timeline.order.request.jsondli.timeline.order.response.json
16dli.timeline.knowsWho-knows-what matrix at a timeline position.dli.timeline.knows.request.jsondli.timeline.knows.response.json
17dli.timeline.episodesCheck episode ordering and report the slack in each slot.dli.timeline.episodes.request.jsondli.timeline.episodes.response.json
18dli.timeline.phasesPhase-walk verdict for an episode.dli.timeline.phases.request.jsondli.timeline.phases.response.json
19dli.export.runRun an export target under a profile.dli.export.run.request.jsondli.export.run.response.json
20dli.name.checkVet a proposed name through the naming oracle before it enters lore.dli.name.check.request.jsondli.name.check.response.json
21dli.attest.missingList questions that lack a current attestation.dli.attest.missing.request.jsondli.attest.missing.response.json
22dli.corpus.importImport a corpus into a document’s store — fact objects on any build, .dli documents on a syntax build.dli.corpus.import.request.jsondli.corpus.import.response.json
23dli.corpus.exportExport a document’s folded fact objects at a head — the live state, not the commit log.dli.corpus.export.request.jsondli.corpus.export.response.json
24author.openOpen an authoring workspace over a scope or fork; returns its id and digest.author.open.request.jsonauthor.open.response.json
25author.statusSummarize a workspace: its staged canonical surface and current digest.author.status.request.jsonauthor.status.response.json
26author.diffShow the workspace’s staged change as structured per-fact diff rows (before/after standing) with findings and derived consequences; the .dli rendering is empty unless a formatter is linked.author.diff.request.jsonauthor.diff.response.json
27author.discardDrop a whole workspace, or one staged declaration.author.discard.request.jsonauthor.discard.response.json
28author.materializeCommit the workspace’s staged fact objects to the lorestore — the accept decision — and return them as JSON (facts and root_hash), with .dli rendering behind rendered:true; an optional decision makes the accepted FACTS certain under it (not carriage claims like rules, same-as, or inertial declarations — those need record_decision plus a cited declaration); refuses while any error-severity finding is open.author.materialize.request.jsonauthor.materialize.response.json
29author.add_entityIntroduce a person, place, thing, or era into the workspace, with provenance (events use author.add_event).author.add_entity.request.jsonauthor.add_entity.response.json
30author.add_factAssert a keyed attribute value on an entity (entity.key = value), with provenance.author.add_fact.request.jsonauthor.add_fact.response.json
31author.add_relationAssert a binary relation between two entities, with provenance.author.add_relation.request.jsonauthor.add_relation.response.json
32author.add_eventIntroduce a chronology event anchored to an era, with provenance.author.add_event.request.jsonauthor.add_event.response.json
33author.add_beforeOrder one event before another, with provenance.author.add_before.request.jsonauthor.add_before.response.json
34author.open_questionFile an open question with its options as tracked debt.author.open_question.request.jsonauthor.open_question.response.json
35author.add_optionAdd one option to a question already open in the workspace.author.add_option.request.jsonauthor.add_option.response.json
36author.add_hypothesisMint a fork-local hypothesis variable for supposition.author.add_hypothesis.request.jsonauthor.add_hypothesis.response.json
37author.supposeSuppose staged hypotheses true within a fork and see the consequences move.author.suppose.request.jsonauthor.suppose.response.json
38author.queryQuery the staged world (base + your in-progress work): what holds about an entity now.author.query.request.jsonauthor.query.response.json
39author.checkRun the full check battery over the staged world — verify your whole draft before materialize.author.check.request.jsonauthor.check.response.json
40author.whyExplain a staged claim’s standing: why it is certain / possible / dead, the blocker, and its repair.author.why.request.jsonauthor.why.response.json
41author.findingsList the workspace’s open findings by severity — what materialize would refuse on, and how to fix each.author.findings.request.jsonauthor.findings.response.json
42author.list_workspacesList your open authoring workspaces and their digests, to recover context.author.list_workspaces.request.jsonauthor.list_workspaces.response.json
43author.branchCreate a persistent branch, or list them — a divergent line of durable writes.author.branch.request.jsonauthor.branch.response.json
44author.mergeMerge a named branch into the current one; returns the merge commit and a structural conflict report.author.merge.request.jsonauthor.merge.response.json
45author.add_dialectDeclare a dialect register — the phonology and name grammar a naming population draws on.author.add_dialect.request.jsonauthor.add_dialect.response.json
46author.add_name_partDeclare a name-part morpheme and its role, the raw material composed names are built from.author.add_name_part.request.jsonauthor.add_name_part.response.json
47author.add_nameCompose a name from name-part morphemes and optionally bind it to the entity that bears it.author.add_name.request.jsonauthor.add_name.response.json
48author.add_termIntroduce a glossary term — a word the lore defines and reuses.author.add_term.request.jsonauthor.add_term.response.json
49author.add_bannedBan a word from the lore surface, with the reason; the guardrail that refuses it later.author.add_banned.request.jsonauthor.add_banned.response.json
50author.add_stateAssert a time-varying state on an entity (a fluent that holds over an interval, not forever).author.add_state.request.jsonauthor.add_state.response.json
51author.add_attestRequest an attestation for an open question — the ledger entry a later sweep answers.author.add_attest.request.jsonauthor.add_attest.response.json
52author.set_standingPromote a provisional stored claim to ratified by citing a ratifying decision.author.set_standing.request.jsonauthor.set_standing.response.json
53author.defeatDefeat a stored claim with a decision while preserving its history and object.author.defeat.request.jsonauthor.defeat.response.json
54author.declare_functionalDeclare a predicate single-valued (a functional dependency), so two distinct certain values for one subject are a contradiction — even for a first-seen predicate canon has no precedent for.author.declare_functional.request.jsonauthor.declare_functional.response.json
55author.assert_same_asAssert two entity ids name the same bearer; the evaluable world merges them, the merge’s standing carried by this claim’s provenance.author.assert_same_as.request.jsonauthor.assert_same_as.response.json
56author.add_ruleDeclare one datalog derivation rule (a typed head :- body clause); every fact it derives carries this rule’s own provenance, defeasible like any other claim.author.add_rule.request.jsonauthor.add_rule.response.json
57author.declare_inertialDeclare a predicate’s fluent values persistent (inertial): a value asserted since a point holds forward until a later, distinct, live value defeats it.author.declare_inertial.request.jsonauthor.declare_inertial.response.json
58author.as_ofProject the inertially-current fluent value(s) at a query point: what holds, and why, including a silent transition’s derived boundary and defeater — the one inertia-aware read.author.as_of.request.jsonauthor.as_of.response.json
59author.record_decisionRecord a baseline ratified decision on the workspace branch so facts that cite it read certain — the wire way to reach certainty and make contradiction checks (fd-violation, fluent, inertia) fire, replacing the fixture-authority hack; defeasible by author.defeat.author.record_decision.request.jsonauthor.record_decision.response.json
60author.predicatesList properties used in the staged world, with their arity and whether they are single-valued or inertial, so you can reuse an existing property name.author.predicates.request.jsonauthor.predicates.response.json
61author.entity_candidatesFind declared characters, places, or other entities with ids close to a name, so you can reuse an existing id.author.entity_candidates.request.jsonauthor.entity_candidates.response.json
62author.assert_predicate_same_asRecord that two property names refer to the same property in your fictional world; the claim can be defeated by a later ruling.author.assert_predicate_same_as.request.jsonauthor.assert_predicate_same_as.response.json
63author.record_decisionsAtomically record many baseline supporting decisions on one workspace branch, validating the complete batch before one commit and one ref update.author.record_decisions.request.jsonauthor.record_decisions.response.json