Sponge guides

A Source is an ordinary graph Entity classified through reviewed vocabulary. The evidence picker searches the current document's space (its private knowledge boundary) and presents human-readable source details. You never paste private graph identifiers or record digests into prose.

1. Choose a Source.Search the authorized graph by visible source identity, type, location, and evidence context.
2. State the bearing.Mark whether the evidence supports, contradicts, corroborates, quotes, reports a method, or provides background.
3. Preserve the selector.Keep the relevant passage, locator, observation, and graph revision bound to the citation.
4. Publish a safe page.Public pages receive ordered evidence markers, callouts, and bibliography data without private graph coordinates. A Source label becomes a link only while an exact artifact grant is active for that publication graph revision.

To cite from a code block, use the code evidence control on the block; it attaches ordered evidence to the block as a whole.

Rich paste rekeys citation clusters in one transaction so copied citations cannot collide. Citation numbers follow current recursive document order, while the verified private evidence rail remains the authority for duplication and publication. Whole-document and block copies containing citations currently stop before a copy is created; see current limitations.

A knowledge proposal is an agent's exact, bounded change set for the knowledge graph. It reaches the review desk at Inquiries with the claim text, the source beside it, and a link back to the document and agent turn. You decide in claim language.

1. Open the proposal.The proposed change set names exact evidence and is parsed before review.
2. Claim the review.Open the stable proposal detail, inspect the exact effect, and take a short-lived review lease (an exclusive right to decide this item).
3. Accept, reject, or return research use.Acceptance derives reviewed Assertions, Evidence, type memberships, provenance, review, and rights records as one recoverable effect. Rejection closes the proposal as attributable history. Returning an agent proposal releases the review with a written reason that the agent receives on your next message; nothing runs automatically.
4. Promote separately.If accepted research should support a public encyclopedia edition, a second review item is created for that purpose.

An edition is an immutable synthesis of reviewed knowledge; a release binds it to a public /k locator. Five separate human acts stand between accepted research and a public page.

1. Stage supported passages.Every passage names one or more reviewed Statements from an exact graph generation.
2. Review the synthesis.Inspect the root, passages, support, omissions, dependencies, identity state, and rights eligibility.
3. Finalize immutably.The accepted candidate becomes a sealed Edition with its own stable identity.
4. Enable publications.The space owner crosses a separate, explicit boundary before any knowledge release is possible.
5. Publish a release.The exact Edition receives a canonical /k locator. A later edition creates a new edition and release.

To withdraw, revoke the release. Withdrawal or tighter rights stop the locator from resolving without mutating the immutable edition or inventing a new history. Public eligibility is checked again when a page is read. Releasing a later edition of the same question does not edit the older page; the older page shows a notice and a link.

Markdown is an import, export, and interchange format. It is not the canonical document model. Before replacing a document, Sponge parses a bounded source, shows the normalized rich preview, and reports syntax or semantics that cannot survive the conversion exactly.

1. Open the document menu.Choose Export… for a copy, or Import… to replace the document from Markdown.
2. Choose the form.Portable Markdown is for other tools; a lossless recovery copy is for restoring this document exactly.
3. Read the loss report.The loss report identifies omitted citation structure, unsupported raw HTML or footnotes, table normalization, internal links, and any source that differs from the canonical preview. A warning never becomes an implicit destructive conversion.

From the API, read GET /api/v1/documents/{documentRef}?format=markdown for the same portable projection with its loss count in the X-Sponge-Markdown-Loss-Count header, or ?format=blocks for per-block Markdown with stable block identifiers. A research report exports the same way from GET /api/v1/research-jobs/{jobId}/report?format=markdown once the report is ready.

A second person's document may cite a first person's released edition or entity. Only released objects can be cited this way, and nothing private in another space is read.

1. Open the evidence picker.Place the cursor where the citation belongs and open the citation evidence picker.
2. Search released objects.Use its Cite a released edition or entity control, which searches released editions and entities from every space by question, passage, or label.
3. Choose one.Choosing it proposes it as a Source in your own space, with the released page as its address and its kind recorded as a Sponge edition or entity.
4. Accept the proposal.After you accept that proposal in review, the source appears in the picker like any other reviewed source, and you cite it as in Cite a source.

A follow-up is a new question that builds on a released edition. Its document cites the edition from the first paragraph, and its Inquiry records the edition as its parent, so the released page can later list what was built on it.

1. Open the released edition.Any edition page under /k has an Ask a follow-up link near its title.
2. Choose the link.Sponge starts a new private document whose first paragraph cites this edition by its question and links to its page, and whose Inquiry records the edition as its parent. Sign in if you are not already signed in.
3. Write the new question.Replace the placeholder question with yours. A research job started on that document keeps the same parent.
4. Release, if you get there.When your edition is released, the parent edition lists it under Built on by.