UnknownAlienHuman/eliot-research

> **Working on this repository?** Start at docs/START-HERE.md — read order,
> authority map, how to claim work, verification gates and branch discipline. The non-negotiable
> boundaries are in AGENTS.md.
**Private owner workspace is deployed** (owner-only URL, not published).
The live owner path imports and reads TXT, Markdown, PDF and DOCX documents, saves projects,
supports exact and lexical search, and runs a full scan of the selected scope. Owner research
executes the 18-stage workflow through an owner-qualified model route, saves a DRAFT,
reopens it from Research history, and verifies its citations against current owner evidence.
The recorded two-document project run produced four SUPPORTED claim assessments while
retaining incomplete scope coverage. Research drafts can also be saved as Wiki proposals,
reviewed, published and reopened through the owner interface. The published Wiki page retains
its coverage limits and the underlying artifact remains a DRAFT. See the
live document/project acceptance.
Release 8b418fe adds Recent work with the latest 20 owner-authorized report,
research completion and Wiki publication events. A new two-document run completed in
about 125 seconds, opened a saved DRAFT and displayed its events in this view. Historical
Wiki events remain readable through current owner reauthorization after the original scope expires.
Release 6f14c0c, with D1 migration fix acebeb9, adds owner editing of published Wiki pages.
Saving creates a separate draft revision; publishing preserves the previous version and records
the edit as unresolved. Both versions of the Orbit page were reopened in the live owner interface.
The Library now shows the project title, with technical scope identifiers in collapsed details.
This establishes the bounded owner path, not full production readiness. Qualification renewal
and policy/pricing expiry constraints are documented in
the local launch checkpoint. Managed semantic retrieval,
Google/MCP admission, the accepted-artifact lifecycle, erasure, federation, recovery and broader
production workloads remain open.
**Pluggable external research federation for ELIOT Memory OS.**
> **Status: active implementation; not production-ready.** The authoritative standalone contract is
> Eliot Research Cloud 29.1, and the language boundary is governed
> by eliotr.language-runtime.v1. Several authority
> paths are implemented and pass deterministic CI, but mandatory product routes and real Cloudflare,
> Google, provider, recovery and workload qualification remain open. See the
> machine-readable implementation status,
> gap register, and
> production readiness plan.
---
What this is
A cloud-hosted evidence library and controlled research system: sources with revisions, a corpus lens,
an evidence-linked research wiki, and governed investigations with explicit coverage accounting.
Four user-facing surfaces:
It serves three genuinely different products that one retrieval pipeline cannot cover:
| Product | Question it answers |
|---|---|
| **Orientation** | What is in this corpus, how is it connected, where should I read next? |
| **Precision** | Give me the exact fragment, number, table, row, page, event or handle. |
| **Materialization** | Assemble an investigation, audit, wiki page or report of practical size. |
What this is not
- **Not a second Memory OS.** It does not own cognitive inheritance, epistemic position, task
authority, canonical decisions or procedures.
- **Not an authority.** Every intelligent result crosses the boundary as an evidence bundle or as
synthesis marked candidate. Nothing promotes itself to truth in ELIOT.
- **Not required.** ELIOT works without it. An absent or degraded federation narrows declared coverage