Ask across the company. Inspect the evidence.

A multi-user, permission-aware company knowledge workspace. It searches approved pages, shows exact citations, consolidates the same field across contracts, records reviewer decisions and keeps an audit trail. No generated legal answer, no customer data, no hidden model.

What this demo is. A live prototype on an encrypted AWS instance, seeded with a fictional company. It is not connected to your Microsoft 365, Google Drive, email or customer documents. Google/Cognito sign-in proves who you are; it does not grant access to your files.

Try this in five minutes

Guest: choose Continue as guest for a read-only tour. The guest sees 11 of 12 pages and no review, audit or source controls.
Cross-contract question: sign in as Alex (owner), open Ask, and search public liability insurance. The Consolidated portfolio table shows each contract’s value, effective date and public-liability position side by side. Differences are shown, not averaged; a blank is not proof of absence.
Verify an original: click a contract in the table. The page shows the exact source name and citation text. The citation is evidence to check; it is not a legal conclusion.
Reviewer flow: sign out and sign in as Priya (reviewer). Open a page, approve it with a note, and see the review bind to the exact content and citations.
Access boundary: sign in as Sam (viewer). Sam sees 11 pages; the restricted Kestrel matter is absent, including from search, aliases and counts.
Export: as Alex or Priya, run a query and download the evidence as Markdown or PDF.
Ingestion: as Alex, use Add my text files and upload the fictional sample contract. The file becomes a private local copy with exact citations; search for the new client name.
Audit: sign in as Jordan (admin) and open Audit to see sign-ins, queries, grants, reviews and exports.

Demo accounts

Person	Email	Password	What they show
Alex Morgan · owner	`alex@example.test`	`alex-demo-password`	Full workspace, ingestion, grants, review/audit
Priya Nair · reviewer	`priya@example.test`	`priya-demo-password`	Review binding, restricted-source visibility
Sam Okafor · viewer	`sam@example.test`	`sam-demo-password`	Read-only scope; restricted page absent
Jordan Lee · admin	`jordan@example.test`	`jordan-demo-password`	Users, sources and audit
Guest	Continue as guest		Read-only fictional demo; no review/audit

Or use Sign in with Google or Cognito: Google is federated through Cognito, then mapped to an existing local account. The local password path remains available. All demo credentials are fictional and must not be reused.

What is live versus roadmap

Capability	Status	Boundary
Permission-aware search, exact citations, aliases, links	Live	Over the pages each principal can read
Consolidated portfolio matrix and conflict detail	Live	Same-field comparison; not a legal interpretation
Content-bound review, stale review, audit, export, read-only MCP	Live	Reviewer decides; audit stores IDs/actions, not text
Multi-user roles, guest, Google/Cognito SSO	Live	SSO proves identity, not provider ACLs
Bounded .txt/.md upload with exact byte evidence	Live	Text only; no Office/PDF/OCR ingestion here
Explicit Google Drive file import + observed ACL mapping	Live in private workspace	One explicit file; exact-user additive mapping; no folder crawl or continuous sync
Microsoft Graph explicit-file import	Built, awaiting tenant	Connector and fake-Graph tests exist; live use needs Entra registration, admin consent and one chosen document
Scheduled Drive/Graph sync + inherited ACL revocation	Roadmap	Needs cursors/webhooks, source health and a first-class grant provenance schema
Scheduled source sync, deletions, currentness propagation	Roadmap	Current demo is historical workspace evidence
Generated consolidated answer / contract interpretation	Not claimed	Extractive evidence only; a reviewer remains responsible

Campbell’s four questions

How does information get in?

Today: approved local text files, bounded uploads and an explicit-file Google Drive import in the private workspace that fetches provider permissions and maps exact users. Next: Microsoft Graph, folder cursors, source health, scheduled sync and revocation. We do not call a copied file “live sync”.

Where is it stored?

This demo is a single encrypted AWS Sydney instance. SQLite data and backups stay on that host; Caddy terminates TLS. No external model receives queries. Production would add a customer-chosen region, encryption-at-rest policy, retention, offsite backup and access review.

How much can I trust it?

Every result is limited to pages the user can read. Citations locate the exact source text. Conflicts are shown, not averaged. Missing evidence is labelled. Reviews bind to content and citations. It does not decide legal effect, coverage or the current agreement.

What about Microsoft?

Microsoft 365 search and Copilot are the incumbent baseline and should be compared on the same real questions. Our edge is the evidence workflow: every contract’s declared position side by side, exact citations, review state, audit and export. No measured superiority is claimed yet.

Why this is different from a chat window

Portfolio-first, not answer-first: the consolidated table exposes the contracts and the gaps before any prose.
Reviewer control: a decision binds the exact content and citations; a later change makes the review stale instead of silently re-approving.
Permission boundary: the restricted page is absent for Sam and the guest, not merely hidden in the UI.
Inspectable path: source, citation, page, review and audit are visible without trusting a generated summary.
Private deployment option: it can run on customer-controlled infrastructure; this demo uses a fictional AWS instance.

Known gaps. No live Microsoft/Google document connection or provider ACL inheritance in this demo. No Office/PDF/OCR upload, scheduled sync, deletion propagation, offsite backup, multi-region HA or independent security review. Google sign-in is via Cognito federation; direct Google on the nip.io hostname is not used. Demo data is fictional and must not be treated as customer evidence.

Use your own agent

The workspace can act as a read-only evidence tool for Claude, ChatGPT, Gemini or another MCP-capable harness. The agent gets search_company_knowledge and get_company_page, while the workspace keeps the permission boundary, citations, review state and audit. The local MCP process is trusted-local only; a remote OAuth surface with per-tool scopes and revocation is available for private deployments but is not published on this demo.

Ask for the agent configuration in a pilot. The prompt pattern is: search first, open the pages, answer only from citations, list conflicts and missing values, and never give a legal opinion.

Next step

Agree one real, redacted source (for example a Microsoft 365 folder of 10–20 contracts), the first users and the exact questions. We compare the same questions against the customer’s existing Microsoft workflow, then run a bounded pilot with a measurable review-time and evidence-completeness result. No live customer system is touched before that approval.

Private prototype. Not a customer commitment, legal opinion or production security acceptance. Open the workspace →