Research · implementations
Seven nested readings. Each one stays inside a source revision and says what that source does not prove.
ai · wdbx · sea · gpu · mcp · tui · 1 sources
Quesar organizes interface, orchestration, retrieval, acceleration, storage, and audit as distinct layers so that evidence and runtime claims can be traced to the component that actually supports them.
ai · wdbx · 3 sources
The private Quesar application implements bounded ingestion, workspace-scoped extraction and search, and consent-gated model access while making degraded retrieval behavior visible instead of silently changing providers.
ai · wdbx · 3 sources
The Quesar mobile Vault keeps one CRUD contract while selecting either the user's private CloudKit database or an encrypted local SecureStore fallback and exposing the selected backend to the application.
ai · mcp · tui · 3 sources
Quasar couples an Anthropic tool loop to a narrowly constrained project filesystem, producing a local application through inspectable read, list, and write operations rather than granting an unconstrained shell.
ai · wdbx · sea · gpu · mcp · tui · 3 sources
Abbey centralizes capability statements in a typed registry whose status, evidence, dependencies, feature flags, and refusal behavior can be projected into documentation and checked for drift.
ai · wdbx · sea · gpu · mcp · tui · 0 sources
WDBX Specimen combines a provenance-aware architecture specification with explicit browser and native runtime profiles, then uses conformance tests to make a bounded subset of the design executable.
ai · wdbx · 3 sources
The Quesar research export pipeline converts validated publication records into stable JSON and static HTML, verifies and copies declared attachments, and records content digests while enforcing unique identifiers, public source URLs, and canonical links.