01
Upload
Add public TXT, Markdown, HTML, CSV, JSON, or text-based PDF material through the private upload boundary.
Files are size- and format-checked before they enter the ingestion queue.
AI support thatactually
Turn approved public support documents into cited answers, measurable retrieval, and a human handoff when evidence runs out. Every public answer stays bound to an immutable release.
Public knowledge only Citations by design Human fallback
Active release is serving
Northstar Help Published support knowledge
AIOP
Hi, I search Northstar's published help guides.
Choose a question to inspect a grounded answer.
What does error NX-204 mean?
NX-204 means the charging case cannot detect the left earbud. Clean both gold contacts, reseat the earbud, and close the case for ten seconds.
AeroBuds setup and diagnostics · Charging faults
Answered from published evidence
Every displayed source is selected server-side.
Built for the public sources your team already maintains
TXTMarkdownHTMLCSVJSONText PDF
A governed evidence loop
From source to support.
Clear at every step.
Uploading is only the beginning. RAGainfra keeps processing, evaluation, and publication separate so unfinished work never silently becomes customer-facing.
02
Process
A fenced worker parses each version into bounded structural chunks. Failed work never replaces what is live.
Only ready source versions can enter the next immutable snapshot.
03
Evaluate
Replay critical questions against the exact draft and compare its retrieved evidence with the published release.
A current manifest-bound regression run is required before publication.
04
Publish
Freeze the approved versions into an immutable release, or keep the current release serving while you improve.
Publication is atomic, and rollback creates another immutable release.
Trust is a system boundary
Your knowledge.
Your release.
Your control.
Original files remain private. Console reads and mutations are scoped to the selected organization and app, while public chat retrieves only from the exact active release.
- Original files remain private and service-side
- Browser mutations require origin and CSRF checks
- Roles and exact app selection scope every console read
- Published citations resolve from release evidence
Simple for visitors, inspectable for operators
Useful support, with the evidence attached.
The visitor gets a clear answer. Your team gets the retrieval, release, citation, and handoff controls behind it.
Grounded answers
Plain-text answers built from selected public evidence.
Structural citations
Source destinations resolved by the server, not the model.
Test Lab
Draft and published retrieval visible before release.
Release control
Immutable snapshots, atomic publication, and rollback.
Human support
Exclusive live handoff with a consented fallback path.
One assistant, three honest moves
It answers. It proves.
It knows when to stop.
RAGainfra separates a polished reply from the evidence needed to trust it. Operators can compare retrieval before release, and visitors can request a person when the workflow demands it.
01
Answer only from approved public knowledge
The public assistant resolves the active release, retrieves its exact snapshot, and renders only server-selected source links.
Grounded answer
Conversation
Inside the selected app and knowledge scope
Mechanics you can verify
Less guesswork. More evidence.
Top 6retrieved chunks measured by the release gate
2 scopesdraft and published evidence kept separate
1 pointeractive release changed atomically
0private customer records in public retrieval
A release you can reason about
The evidence path, mapped.
The old release remains active while new material is processed and tested. Only a current passing manifest can move the serving pointer.
01
Source
Public material uploaded
The operator attests that each file contains support knowledge any visitor may receive.
02
Worker
A ready draft is built
Bounded structural chunks are staged and committed only by the current fenced attempt.
03
Test Lab
Critical questions are replayed
The run records draft and published retrieval for the exact current source manifest.
04
Release
An immutable snapshot serves
A compare-and-swap publication changes the active pointer without rewriting release history.
Boundaries, not slogans
Designed around verifiable truths.
The product contract makes important states visible instead of asking your team to infer them from a confident answer.
A ready source is not automatically a published source.
Release controlIngestion, evaluation, and publication remain distinct states.
The model never chooses an arbitrary citation destination.
Evidence integrityRendered links resolve from request-selected chunk identities.
Human support owns the channel until the visitor closes it.
Handoff boundaryAssistant persistence is blocked during the exclusive workflow.
Start with one narrow assistant
Build the evidence loop first.
Create a private workspace, add a public source, inspect the draft, and publish only when its current regression passes.
Private source storage Draft Test Lab Immutable releases
Free workspace limit
Create workspace 3 apps
Database-enforced capacity in the current release.
Before you publish anything
The practical questions.
Clear answers about public knowledge, releases, citations, product limits, installation, and human handoff.
Already have a workspace?Sign in to continue from the selected app.
The current product is deliberately public-knowledge-only. Published sources may be shown to any visitor of that app. Private customer records, account details, order data, and internal confidential documents stay outside the retrieval scope.
No. Upload and ingestion create a ready source version. Operators test the exact draft, pass the current retrieval gate, and explicitly publish an immutable release. A failed or partial ingestion leaves the active release untouched.
Every displayed citation is resolved from server-selected evidence. Test Lab also records ordered draft and published chunk IDs, source titles, headings, bounded excerpts, retrieval counts, and durations for each unchanged regression case.
The assistant can ask for clarification, state that evidence is insufficient, or offer human support. It is not allowed to manufacture a source, activate a model-authored link, or use another release's citation.
No. RAGainfra does not execute generated code, access private account or order records, or perform consequential commerce actions. Expanding into authenticated tools would require a separate authorization model and threat assessment.
The preferred widget keeps chat on your website through a verified support subdomain on the same site, an exact parent-origin allowlist, and a sandboxed iframe. It loads chat only after a visitor opens it. When that domain setup is unavailable, the compatibility launcher opens the same hosted assistant in a secure new tab.
Bring one source and one hard support question.
Build the first draft, inspect what it retrieves, and keep the public route closed until you are ready to release it.
Start with one public knowledge base
Create your private operator workspace.
Confirm your email, name the organization and first assistant, then add a source. The public route stays unavailable until you evaluate and publish it.
No document becomes public without an explicit release.