Source-Grounded Assistant | AI Capability Playbook

Choose mode Ask Read answer Review citations Inspect details

Ask

Ask The Package

Loading approved public corpus metadata...

Source boundary

Package-only means approved playbook material only.

Ask the Package answers from the approved playbook material loaded with this site. This is the AI Capability Playbook package. It does not browse the internet, use private files, or treat model memory as evidence.

If the package does not support the question, the assistant should say so and show the citation or refusal basis. Generated answers are interpretation, not evidence or approval. The site is for readers. The corpus is for grounding. The assistant is for interpretation. The model is not the source of truth.

The playbook is field guidance, not final company policy. This page does not approve tools, data classes, workflows, production use, enterprise deployment, providers, or models. Cloudflare Access and durable edge rate limiting are external deployment controls, not browser-only gates or client-side-only protection.

Mode

AnswerDirect package-grounded answer. ExplainPlain-English walkthrough using package guidance. AssessEvaluate a pasted proposal against package criteria, gaps, and risks. Find evidenceStrongest supporting package sections with minimal synthesis.

Mode guide: which mode should I use?

AnswerUse when you need a direct package-grounded answer.

ExplainUse when a concept needs a plain-language walkthrough.

AssessUse when a proposal needs criteria, gaps, risks, and review boundaries.

Find evidenceUse when you need the source basis first and minimal synthesis.

Citations/refusalEvery run should show source basis or a deterministic refusal state.

Question or proposal

Normal users do not need to choose source IDs or source packs. Source routing remains governed and package authority does not change.

Advanced: operator source routing controls

Source context

Package onlyDefault. Approved package citations or refusal. Package + current contextExplicit gated proof. Current retrieval and synthesis require server-side cited sources.

Current/public context

Enrichment sources

Loading approved enrichment source registry...

Use approved current/public sources to add context to this answer. Package sources remain the authority for package claims. Enrichment sources do not change the package.

Package claims come from approved package sources. Enrichment sources provide current/public context only.

Choose the enrichment profile. Backend routing resolves eligible sources for this answer.

Enrichment source cards will appear after the registry loads.

Governed registration

Request new source

System-wide enrichment sources require governed registration, source validation, allowlist rules, extraction profile, validation receipt, and owner approval.

Admin-gated in this proof.

Answer

Grounded Answer

Read the grounded answer first, then review refusal state, citations, source scope, and operator details as needed.

No request submitted.

No completed run yet.

Refusal Or Not-Found State

No refusal

Citations And Provenance

Citation cards show package evidence separately from current/public enrichment and session-only pasted source text.

Source telemetry

Answer Source Scope

No run yet

Run scopeNo completed run yet.

GroundingNo completed run yet.

EnrichmentNo completed run yet.

Session-only pasted sourceNo completed run yet.

Operator detailsNo completed run yet.

Source evidence lane

Package authority and current/public enrichment

No run yet

Current/public source content is enrichment only. It is not package authority.

Package authority No completed run yet.

Current/public enrichment No completed run yet.

Run diagnostics Token usage and compact run summary are secondary.

Token usage Prompt: not observed Completion: not observed Total: not observed

Compact run summary

Client build:20260625-195

Mode:Answer

Context mode:Package only

Provider state:not called yet

Provider:not called

Model:not observed

Total tokens:not observed

Selected sources:0

Current citations:0

External retrievals:0

Retrieval state:not requested

Refusal/not-found:none

Latency:not available

API response:not available

Direct provider calls:0

Direct current calls:0

API calls:0

Advanced run details, source selection, request package, and corpus inventory

Operator source mechanics

Advanced: source selection preview and last-run source details

Preview estimates likely sources before you run. Sources used in the last answer are the actual completed-run source basis.

The assistant scores package sections against your question, balances source families, and keeps up to 8 sources. Preview is estimated before a run; last-run sources are what the completed answer actually used.

Source scoring is query-driven. Source-family balancing may diversify the set. Up to 8 is a cap, not a target every answer must hit. Draft Source Preview is not final until Ask completes.

Preview: likely sources if you run thisDraft Source Preview

Source preview will appear after corpus metadata loads.

Sources used in the last answer

Last-Run Selected Sources update only after a completed answer or refusal.

No completed run yet.

Run Telemetry

Durable telemetry, database logging, model-routing history, and tokenomics analytics belong to #189 unless a later issue expands scope.

Token counts are shown when returned. Estimated run cost is deferred to #189 because cost calculation must be driven by provider and model pricing configuration; this page does not implement a token-cost calculator.

Detailed run telemetry

Operator detail stays readable in wrapped cards. Long values wrap here, while JSON and request package content stays contained in its own scroll box.

Corpus Inventory

Corpus inventory will appear after metadata loads.

Required Refusal Patterns

Not found in the approved playbook package.

The playbook provides guidance, but it does not approve this tool, data class, workflow, production use, or company policy.

The submitted proposal lacks enough evidence to assess this criterion.

Draft Proof Request Package

What is this for?

This is the evidence package prepared for the server-side provider call. Use it to audit selected source evidence, reproduce or debug a run, inspect grounding boundaries, or understand why the assistant answered or refused.

It is not the final answer and it is not the provider response. It may exist before a provider call because the browser can prepare candidate source evidence first. It carries checked package snippets, citation metadata, refusal rules, and the derivative-output label.

{}