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 fictional company records and licensed historical public references. 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.

Latest checks were HTTP/API smoke tests, not a fresh rendered-browser acceptance test. Reviewer, upload and administrator walkthroughs were not re-tested in this check.

Try this in five minutes

Guest: choose Continue as guest for a read-only tour. The guest can search the permitted baseline and has no review, audit or source controls. A 12 November 2026 HTTP check searched 727 readable pages and listed 15 readable sources.
Cross-contract question: continue as guest, 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.
Inspect the recorded citation: click a contract in the table. The page shows the exact source name and citation text. Seeded citation text is a reference to inspect, not proof that original-file bytes were retrieved or that a legal conclusion follows.
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). The restricted Kestrel matter is outside Sam’s readable scope, including search, aliases and counts.
Export: as guest or another authorized reader, 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.

Before trying a private workspace. Use only the named partner link and an explicitly invited identity. Private hosts have no guest access. Sign-in is separate from permission to connect Drive or upload documents. Start with fictional or approved redacted files; do not use customer data until the pilot’s access, retention and recovery terms are agreed.

Personal demo account

On the sign-in page, choose Create a personal demo account to get an isolated, read-only viewer for the public document set. No email or password is required. The account lasts 24 hours, sees only the public sources shared with the guest account, and is separate from every other visitor. Sign in with a named account or SSO for role-specific features and private pilot workspaces.

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 an explicitly configured identity is mapped to an existing local account. A Google login does not create a private workspace or invite anyone automatically. The local password path remains available. All demo credentials are fictional and must not be reused.

What is live versus roadmap

Private Drive capabilities describe the 9 November pilot receipt; 12 November checks verified host health and authentication configuration only, not participant sign-in, Drive consent, refresh operation or backup freshness.

Capability	Status	Boundary
Permission-aware search, exact citations, aliases, links	Live	Over the pages each principal can read
Consolidated portfolio matrix	Live	Different contracts are portfolio comparisons, not contradictions. Conflict candidates require matching explicit comparison scope; no legal interpretation is made.
Content-bound review, stale review, audit and export	Live	Role-scoped controls; a reviewer decides. Remote MCP/OAuth remains disabled on this public demo.
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
Google Drive folder/file intake and observed exact-user permissions	Private pilot only	Separate participant consent; Google test-user restrictions apply. The public demo has no Drive connection.
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
Bounded Drive refresh and source changes	Private pilot only	15-minute, 100-file refresh; changed content stales reviews, deletions pause sources, and invalid authorization is handled. Group/domain permissions and participant ACL-change testing remain limited. Graph is not live.
Shared baseline in separate partner workspaces	Deployed 11 November	Baseline pages are copied into separate tenant volumes; private pages, credentials, users, sessions and audit remain local. A refresh heartbeat does not prove provider currentness.
Generated or experimental synthesized answers; converted ERAIS model	Not serving	The public route returns evidence and portfolio comparisons. The newer answer layer remains under qualification. A reviewer remains responsible.

Campbell’s four questions

How does information get in?

The public workspace uses its approved demonstration baseline and bounded text uploads. Separate private pilots support consented Drive folder/file intake, exact-user permission handling and bounded refresh. Microsoft Graph still needs a qualified live tenant. Refresh and observation times are not proof of continuous currentness.

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 show the recorded source text. Portfolio differences are shown, not averaged or silently classified as contradictions. 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 an AWS instance containing fictional company records and historical public references.

Known gaps. No live Microsoft/Google document connection in the public demo. No Office/PDF/OCR upload, offsite backup or multi-region HA is claimed. Bounded pilot acceptance checks are not a production security audit. Private participant login and backup freshness require a release-time check; Google Drive consent has test-user and unverified-app restrictions. Google sign-in is via Cognito federation; direct Google OAuth on the workspace.neuroforge.io hostname is not used. Fictional company records and historical public references must not be treated as current customer evidence.

Use your own agent

A configured private deployment can expose read-only evidence tools to a compatible MCP client; client-specific interoperability needs verification. 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 →