# Using Sponge

How to save and highlight articles and PDFs in Sponge, write in a document with your agent, and check its sources before you share.

Docs edition 2026.09. Reviewed 30 September 2026.

- [Save your first article](https://sponge.computer/docs/start): Keep a copy, highlight a passage, and add a note.
- [Read your Following archive](https://sponge.computer/docs/guides#following): Review the saved candidates after hosted monitoring retired.
- [Connect your own agent](https://sponge.computer/developer): Use the research skill or make your first API call.

## Your library, your reading

Start with an article or PDF. Keep the source and your notes together.

Library holds the articles and files you save. To read keeps unread items handy; All saved includes what you’ve read. Archive puts an item aside without removing its copy, highlights, or notes.

### Your library

Save articles and files for later. Open a saved copy to read, highlight a passage, or add a note.

Sponge interface · fictional notes and sources
Example screens; nothing is sent or published.

[See the Sponge interface](https://sponge.computer/docs#preview-library)


The reader shows the saved text. Select a passage to highlight it, add your own note, or copy it into work with your own agent. Sponge keeps the saved text and its source details available for review.

Documents is for writing and longer research with your own agent. Your library is private; sharing a document does not share your source archive.

To use a passage in a document, select it and choose Add to document. Pick a document, review the passages, then choose Add passages. Find the copies under Document actions → Sources. Collaborators can read the copied passages; your full Library item, other highlights, and private notes are not shared. The document keeps its copies if you later remove the Library item.

In a document, select a source citation to open its copied passages in Sources.

## Write and research in a document

Start with a private document and use your own agent when you want help.

Your document has an editor for writing and retained conversation history. Start with a question, notes, or a draft, then work with your own agent. You can write without starting hosted research or publishing anything.

1. Write: Write a question, notes, or a draft. Attach sources when useful.
2. Research: Ask your own agent to investigate a question and retain its sources.
3. Review: Read the sources and compare conflicting evidence. Check the agent’s edits in History.
4. Share when ready: Invite a collaborator or publish a saved version. Research editions have a separate release process.

Use your own agent to investigate and write with Sponge’s document and source tools. GhostGet handles local source capture and access; you choose the evidence to retain in Sponge. Fresh hosted chat, report jobs, and source analysis are retired. Saved sources, conversation history, and historical results remain available; already accepted work can finish or be cancelled. Cite the exact passages you use and keep their coverage limits visible.

Use the save indicator to check your changes. Headings, paragraphs, lists, tables, and code are editable blocks; moving or nesting them preserves their links.

Open Document actions beside the title, then choose History to inspect or restore earlier versions. The same menu contains Tags and Document changes. Use Editor tools above the document for its outline, citations, import, and export.

Conversation history preserves accepted turns and their final state. If an accepted response is still active, you can stop it from the history pane.

Use your own agent to handle new questions, attachments, and follow-up work with Sponge’s document and source tools.

## Sharing and visibility

Choose who can read your work, which version is public, and how the published set can travel.

Your document starts private. Share gives a named person access to the document or a block. It is also available in Document actions. To make a read-only copy public, open Document actions and choose Publish document.

Later edits do not change the public copy. Choose Update public version in the Publish document panel to replace the public copy, or Unpublish document to remove public access. These actions do not change collaborator access.

Changing a document’s title keeps its existing links and public copy.

### Publish document

Share the saved version of a document. Later edits stay private until you update its public version.

Sponge interface · fictional notes and sources
Example screens; nothing is sent or published.

[See the Sponge interface](https://sponge.computer/docs#preview-publication)


People with edit access can write in the same document. Changes appear as they save. The editing indicator identifies activity in the current block, including another tab of your own.

Conversation history and retained paper records belong to the document owner. Collaborators see changes once they are applied to the document.

If edits cannot be combined, Sponge stops saving and keeps your unsaved copy. Choose Download unsaved copy to keep it, then Open saved version. The recovery notice keeps your copy available until you choose Discard unsaved copy.

- Private workspace: The owner and people explicitly granted access can read the document and its private Inquiries.
- Shared document or block: Named people can read or edit the shared text. The owner’s chat, attachments, and pending agent suggestions stay private. A forwarded link does not grant access.
- Published document or block: The chosen version becomes public and read-only. Later edits do not change that public version.
- Static public mirror: An operator can republish every public document and block page as a portable read-only static site. The copy keeps canonical links, publication dates, and bibliography data; private workspaces never enter it.
- Accepted knowledge proposal: Reviewed claims, evidence, and decisions are added to private research. Acceptance does not publish them.
- Promotion review: A separate review decides whether accepted research can be used in a public encyclopedia edition.
- Released edition, entity, or Inquiry: Reviewed research becomes readable at a public /k address only after publication is enabled and a release is made.

Public pages exclude chat, private tags, sharing permissions, hidden evidence, and later private edits. Reviewed research editions use a separate release process.

An operator can also export the published set as a portable read-only static site hosted on ordinary static storage. Mirror pages keep their canonical sponge.computer links, publication dates, and bibliography data, and navigation and search run in the reader's browser. The mirror is rebuilt from current publications, so an unpublished page disappears from the next export; nothing outside an existing publication can cross into the copy.

## Review agent changes

Choose whether agent edits apply directly or wait for your review.

Document changes are saved in History. Review changes from your own agent before you save, share, or publish them.

Open Document actions to inspect history and review the document before publication.

- Open Document changes from Document actions to inspect additions, edits, and deletions. Accept or reject a block, or choose Accept all or Reject all for the turn.
- In Inquiries, review proposed claims and their evidence. This is separate from editing the document.

Rejecting a document change leaves your text unchanged. A change that conflicts with newer work cannot be accepted, and the agent cannot accept its own proposals. Accepted document edits become visible to collaborators. Accepted knowledge proposals stay private; public editions need a separate promotion review and release.

## Check the sources

Check what a source contains before treating it as evidence.

Open Sources before relying on a finding. It shows the title, year, evidence kind, and saved excerpt when available.

- Page highlight: a passage from a page the research opened.
- Abstract: a paper summary that may omit methods or results.
- Search highlight or search excerpt: a lead whose page was not opened.
- Registry summary or metadata only: a record of existence, identity, dates, status, or sponsorship.

A search result alone cannot support a finding, and metadata does not establish study results. Claims without usable excerpts are recorded as gaps. Expand excerpts to read their exact words and retrieval dates. Sources consulted lists sources considered but not cited.

## Inspect agent memory

Inspect the notes the agent keeps during a run, or remove them.

Open Document actions, then choose Memory to inspect the agent’s working notes, the reviewed knowledge it had in view, and when the notes expire.

- Only the document owner can see working memory. Sharing or publishing the document does not include it.
- Each run has its own session. Notes stay in that document and expire within a day of the session starting.
- Remembered notes are not evidence. They need review before supporting a claim or citation.

Forget now removes the session’s memory before expiry. The next run starts without those notes. Chat cards link to the panel when the agent remembers or recalls something.

### Agent memory

Inspect retained working notes and their expiry. Forget now removes those notes while keeping your document and conversation history.

Sponge interface · fictional notes and sources
Example screens; nothing is sent or published.

[See the Sponge interface](https://sponge.computer/docs#preview-memory)


## Organize reviewed research

Use Inquiries and editions when you need a reviewed research record.

An Inquiry keeps a question, findings, gaps, and review decisions together. An edition is a fixed, reviewed answer with cited passages. You can use the editor and chat without creating either.

Save sources and notes before choosing classifications. An Entity can have several types, and competing claims keep their own sources and Contexts.

The vocabulary definitions use Oh’s open research format, so independent tools can use them outside Sponge. Sponge keeps your documents and review decisions in its workbench.

In Inquiries, open Vocabulary profiles to preview a profile and its dependencies, then install the version you want to use. Available profiles and installed profiles are shown separately. Upgrading a profile keeps older claims linked to their original definitions.

Qualified profiles check the subjects and objects of a relation: a recording records a performance, while an assay tests a sample. Shared units, calendars, identifier schemes, and version relations keep these claims precise without forcing every Entity into one type.

Install Identity and context to record an attributed identity claim, its identifier scheme, and supporting evidence, or to describe time, locations, values, and provenance. An identifier match does not merge Entities. These records preserve stated context without converting units, calendars, or coordinates.

Install Cross-domain links to connect records across profiles: an offer identifies its product, an assay names a method and finding, a track identifies its recording, a trajectory includes attempts, and a task identifies its goal. Preview its dependencies before installing; it brings 19 dependency packs.

Install Measurement results to connect software results, observations, research findings, or backtests to quantities and their context. A benchmark result can name its exact model version, metric definition, dataset split, method, and evidence. A cloud-altitude measurement can retain units, bounds, time, location, and its stated reference surface. These links do not establish comparability or calculate conversions.

Install Monetary values and quotes to follow an offer price to a decimal amount, identified currency, quotation basis, and any stated tax treatment or effective interval. Missing conditions remain unknown. Financial quotes have their own listing, kind, and observation time. This extension brings 20 dependency packs through Cross-domain links; preview that dependency list before installing.

Install Content occurrences to connect a text usage to its form, contextual sense, and language, or to locate an attributed allusion or depiction. A source-native locator qualifies the link to one exact retained version. That version identifies the containing source or artifact and a media value with the retained content digest. Your source tools must still verify those bytes; a URL or capture time alone is insufficient.

Install Participation roles to distinguish an adviser from an executive, or a mixer from a performer. Each participation identifies an agent, its exact contribution subject, and the role a source attributes to it. Keep separate records for different dates, recordings, or editions. A credit does not establish employment or ownership.

Your own agent can request a focused profile from the available catalog or your space's installed definitions. Each result identifies the selected versions, dependencies, definitions, and guidance for following relationships. The guidance does not run a query or validate a completed answer. Installed profiles preserve the versions your space actually uses.

Your own agent can discover the catalog, submit typed claims with qualifiers and actual or hypothetical Contexts, and read permitted private knowledge. New claims stay proposed until you review them.

Accepting a new external proposal for private research and search lets agents with read access search its claims and evidence in that space. Existing restrictions still apply, and public use requires a separate decision.

For Wikidata, provide a captured entity response to the import preview. Sponge preserves source revisions, statement ranks, qualifiers, references, language, precision, calendars, and missing-value distinctions. Unfamiliar properties retain their original source identities. The ontology coverage command exposes supported datatypes, separate mapped and preservation-only property counts, use-case profiles, and remaining gaps. A preview reports its coverage and omissions; it does not establish truth or fetch a source.

Install Source relationships to describe what a source attributes to an Entity. For example, a source can name an author of a work without assigning either Entity a local domain type. The expanded Wikidata mapping preview offers 15 reviewed relations and reports unmapped statements separately. The latest catalog also identifies 16 preservation-only properties; those entries retain source data without a local mapping target. This inventory does not limit which properties a bounded capture can preserve. You still choose local identities and review each proposal; source attribution alone does not establish a claim as true.

- Language: Lexemes, forms, senses, translations, and attested uses.
- Culture: Motifs, depictions, allusions, fictional subjects, and naming explanations.
- Natural world: Occurrences, classification schemes, observations, and features, including clouds.
- Body: Bodily phenomena, reported experiences, populations, and mechanism hypotheses.
- Research: Publication versions, studies, methods, samples, findings, and corrections.
- Substances: Substances, batches, assays, supply-chain steps, and dated vendor offers.
- Organizations: Company history, roles, transactions, and milestones.
- Events and news: Events, stories, coverage, and attributed editorial judgments.
- Software and AI: Software versions, models, harnesses, protocols, and evaluation results.
- Music: Works, performances, recordings, releases, and credits.
- People: Attributed profile records, relationships, and purpose-bound contact details.
- Finance: Instruments, listings, observations, strategies, and backtest assumptions.
- Formal systems: Rules, initial states, executions, and proof artifacts, including cellular automata.
- Agent work: Tasks, attempts, trajectories, skills, checks, and resumable outcomes.
- Source relationships: Source-attributed authorship, creation, subjects, stated bases, versions, editions or translations, languages, genres, performers, parts, stock exchanges, taxa, and programming languages.
- Identity and context: Attributed identity claims, identifier schemes, time, locations, evidence, values, and provenance activities.
- Cross-domain links: Typed links between offers and products, tracks and recordings, profiles and accounts, simulations and snapshots, and other research objects.
- Measurement results: Reported quantities with exact metrics, model versions, dataset splits, methods, time, locations, and evidence.
- Monetary values and quotes: Decimal amounts and identified currencies, package or quotation bases, offer conditions, and separately dated financial quotes.
- Content occurrences: Text forms, senses, and languages, with lexical uses, allusions, and depictions located in exact retained content versions.
- Participation roles: Source-attributed roles in organizations and contributions to exact events, works, recordings, or editions.

### Offline public research exchange

Convert an explicitly selected public Soulscrape research exchange into an Oh research packet offline. The exchange is limited to 512 KiB, 256 sources, 256 claims, and 16 source references per claim. Conversion measures the deduplicated output and rejects it only when the actual packet exceeds 1,024 records; it never truncates the exchange.

The packet preserves the publisher-scoped profile URL, supplied subject identity, source catalog, asOf and generatedAt timestamps, and the claim labels fact, stated_belief, pattern, and speculation. A supplied Wikidata identifier remains an asserted identity, not proof of a match. Source dates keep their original precision, and source URLs keep their supplied spelling. Claim text that is not NFC uses an explicit NFC projection for the Oh text value while preserving the original UTF-8 bytes and digest in context. Citations remain publisher-supplied references rather than independently observed evidence.

The omittedCollections list names timeline, themes, works, appearances, relations, openQuestions, and body. These collections are omitted, not empty. The subject summary is also excluded because it has no separate claim citations. The original packet digest is an external commitment; conversion cannot reconstruct the omitted bytes.

The output has unasserted authority and proposed claims. Structural verification does not establish factual truth, even for first-person sources. Conversion does not write to working memory, fetch sources, accept claims, publish content, or grant review or content rights. Review and permission decisions remain separate.

### Research terms

- Entity: The subject of research, such as a paper, person, or place.
- Statement: A claim about a subject, kept as a fixed record.
- Assertion: Someone’s position on a claim, with its purpose and context.
- Evidence: A source or observation and how it relates to a claim.
- Context: The conditions under which a claim applies, such as a time, place, or study population.
- Inquiry: A question and the record of work done to answer it.
- Projection: A view or fixed edition made from a specific set of reviewed records.

Use /inquiries to review claims or prepare an edition. Browse /k to read released editions and their cited passages. Public search excludes private documents and unreleased work.

## Other docs pages

- [Start: Start with Sponge](https://sponge.computer/docs/start)
- [Guides: Sponge guides](https://sponge.computer/docs/guides)
- [Reference: Sponge reference](https://sponge.computer/docs/reference)
- [Status: Status and limits](https://sponge.computer/docs/status)
- [Sponge developer resources](https://sponge.computer/developer)
- [OpenAPI 3.1](https://sponge.computer/openapi.json)