fieldwork

A workshop for community schema curation on atproto. Built on idiolect.

fieldwork composes the records that govern how a community translates between atproto schemas. Seven tools share one in-memory workspace: authors compose dialects, vocabularies, communities, recommendations, and deliberations against the dev.idiolect.* lexicon family, browse the lexicons themselves, and upload protolab-authored panproto lenses to their own PDS. Drafts export as record JSON, copy as idiolect-cli invocations, or publish straight to the active session via atproto OAuth.

Live at https://idiolect.dev/fieldwork/

Tools

Seven tools, all working off the same in-memory Workspace so an import in one tool feeds suggestions in the next.

Tool	What it builds	Record kind
Dialect Composer	A dialect with preferred lenses, deprecations, and supersedes-chain.	dev.idiolect.dialect
Vocabulary Editor	A typed multi-relation knowledge graph (OWL Lite property characteristics + SKOS Core annotations) or the legacy action / purpose tree.	dev.idiolect.vocab
Community Config	A community with members, role assignments, conventions, endorsements, core lens / schema sets, and record-hosting policy.	dev.idiolect.community
Recommendation Builder	A recommendation with a lens path, condition tree, and required-verifications block.	dev.idiolect.recommendation
Deliberation Composer	A community-scoped question or proposal under collective consideration, plus statements and observer outcomes.	dev.idiolect.deliberation{,Statement,Outcome}
Lens Manager	Lists your published lenses and uploads protolab-authored bodies to your PDS.	dev.panproto.schema.lens
Lexicon Browser	Read-only view of every bundled dev.idiolect.* lexicon plus user-imported docs.	(read-only)

Every editor has the same import / export shape. Paste an at-uri, drop a JSON file, or pick from the bundled fixtures. Export downloads a JSON record body, copies an idiolect-cli publish command, or publishes straight to your PDS via OAuth.

Why static-only

idiolect is a federated record system. Everything fieldwork builds is a record draft conforming to one of the dev.idiolect.* lexicons. Publishing means appending the record to the user's PDS, which only the user can authorise. Keeping fieldwork backend-free (static HTML + CSS + JS + WASM, hostable on GitHub Pages) means:

• no fieldwork-operated server holds drafts or credentials.
• import / export works against any PDS the user can OAuth into.
• the tool is reproducible and forkable: clone, push to your own Pages, redirect a custom domain.

Running it

Hosted

https://idiolect.dev/fieldwork/

Locally

Requires Rust 1.95+, Node 20+, and wasm-pack.

git clone https://github.com/idiolect-dev/fieldwork
cd fieldwork
./scripts/build-wasm.sh     # builds the fieldwork-wasm crate
cd app && bun install && bun run dev

Rust changes need a rebuild of the WASM bundle (./scripts/build-wasm.sh). The React layer hot-reloads.

At-URI autocomplete

Every at-uri input understands handles. Type aaron.bsky.social/..., pick a record from the live PDS listing, and fieldwork stores the canonical at-uri internally. On serialise (export, publish), the handle's repo segment resolves to a DID via bsky's public AppView so the bytes that hit the network always carry stable identifiers, even though the input shows the human-readable handle.

The autocomplete walks segments in order:

1. Handle / DID search across local sessions and bsky typeahead. When an expectedCollection is set, the active session's records of that kind appear at the top.
2. Collection segment, prefix-filtered against the bundled record NSIDs.
3. Rkey segment, live from the typed repo's PDS via com.atproto.repo.listRecords.

Lexicon viewer

Six tabs over the active lexicon document:

• JSON: syntax-highlighted source.
• Definitions: table of every def entry with its type and description.
• Fields: per-def field tables, with refs and array<ref> and unions recursively expanded as indented child rows. Cycle-safe.
• Refs: a per-def "uses" / "used by" table. Clickable internal refs jump to the Fields tab and scroll to the target.
• Diff: pin a baseline version and surface added / removed / changed fields against it.
• Try: a copy-pasteable record body or curl-able request stub for the lexicon's main def, filled with placeholder values that substitute the active session's DID and PDS when signed in.

OAuth scopes

fieldwork uses atproto's granular scope spec. Three intent tiers are surfaced in the Sign-in menu:

Intent	Scopes
read-only	atproto
curator	atproto repo:dev.idiolect.{dialect,vocab,community,recommendation,deliberation,deliberationStatement,deliberationOutcome} repo:dev.panproto.schema.lens
full	atproto + every repo:dev.idiolect.* collection plus the lens scope

Once dev.idiolect.auth.{curatorAccess,fullAccess} permission-set lexicons are published and resolvable, set VITE_USE_PERMISSION_SETS=true at build time to switch to the more-readable include: references.

Layout

crates/
  fieldwork-core/   record-draft model, validators, in-memory workspace
  fieldwork-wasm/   wasm-bindgen entry points the React app imports

app/
  src/
    tools/          one component tree per tool (DialectComposer, ...)
    workspace/      shared workspace state (zustand)
    sessions/       atproto OAuth client, scope tiers, publish + normalise helpers
    components/     AtUriAutocomplete, HandleSearch, GuidancePane, DiffPane, ImportButton, ExportButton, SessionMenu, Sidebar
    lexicons/       LexiconViewer + bundled dev.idiolect.* + dev.panproto.* JSON
    fixtures/       seed data for each tool
    panproto/       wasm init + lexicon validator

Each crate is a thin wrapper over idiolect. Most idiolect releases land in fieldwork as a Cargo.toml tag bump.

Tests

cargo test --workspace      # Rust
cd app && bun test          # frontend (vitest)
cd app && bun run typecheck # tsc --noEmit

License

MIT. See LICENSE.

Related

• idiolect: lexicon family, codegen, record indexer, observer, orchestrator. fieldwork is the authoring surface on top.
• protolab: the visual lens editor. Export a lens here, upload it via fieldwork's Lens Manager.
• panproto: schemas, lenses, protolenses, the foundation under both idiolect and protolab.
• atproto: the protocol fieldwork's records publish into.