sincLLM operator guide · evidence packet

Private AI Brain Evidence Packet: What to Capture Before a Decision

Assemble reviewable evidence for a local retrieval-augmented knowledge system without turning assumptions or producer claims into proof.

The direct answer

Assemble reviewable evidence for a local retrieval-augmented knowledge system without turning assumptions or producer claims into proof. The working output is A claim-to-evidence packet with provenance, freshness, contradiction, and NOT_TESTED fields.

For Private AI Brain, the bounded capability is a local retrieval-augmented knowledge system. Begin only when the team can supply approved documents or data exports, access rules, answer use cases, and evaluation examples. The documented delivery target is a local-model RAG system checked by a QA agent; anything broader requires a new scope and a new authority decision.

The copyable evidence packet

This evidence packet is for teams that need answers grounded in owned documents while keeping the retrieval and model path inside their infrastructure. It begins with approved documents or data exports, access rules, answer use cases, and evaluation examples and stays inside the documented workflow: source inventory, access classification, parsing, chunking, indexing, retrieval, answer generation, citation checks, evaluation, and refresh. For Private AI Brain, the evidence packet remains reviewable because its decisions have named owners, evidence fields, and stop conditions.

The Private AI Brain evidence packet keeps each claim separate from its source and from the reviewer decision that accepts or rejects it. For this evidence-packet task, a URL or file name supplies provenance but not automatic proof; an executor saying “done” remains an assertion until a separate observation supports the exact criterion.

IDClaimExpected source classRequired provenanceStarting statusFreshness rule
CLM-01Sources and access classes are inventoried.buyer-environment observationrecord path, observer, time, and methodNOT_TESTEDReopen after input, configuration, owner, or environment change
CLM-02Retrieval permissions match source permissions.buyer-environment observationrecord path, observer, time, and methodNOT_TESTEDReopen after input, configuration, owner, or environment change
CLM-03Answers cite claim-level evidence.buyer-environment observationrecord path, observer, time, and methodNOT_TESTEDReopen after input, configuration, owner, or environment change
CLM-04Deletion and refresh propagate to the index.buyer-environment observationrecord path, observer, time, and methodNOT_TESTEDReopen after input, configuration, owner, or environment change
CLM-05Adversarial documents are included in tests.buyer-environment observationrecord path, observer, time, and methodNOT_TESTEDReopen after input, configuration, owner, or environment change
CLM-06Local deployment reduces some egress paths but does not make the data correct, the retrieval complete, or the answer safe. Access control, backups, logs, and operators remain part of the threat model.accepted sincLLM product truthrecord path, observer, time, and methodCONFIRMED_BOUNDARYReopen after input, configuration, owner, or environment change

Machine-readable evidence row

{
  "claim_id": "CLM-01",
  "claim_type": "OBSERVED",
  "content": "Sources and access classes are inventoried.",
  "evidence": "attach a direct readback or test receipt",
  "provenance": {
    "source": "named path or system",
    "observed_at": "ISO-8601",
    "method": "inspection or test"
  },
  "status": "NOT_TESTED",
  "contradictions": [],
  "reopen_if": "restricted documents placed in a shared index"
}

Contradiction rule

When two admissible records disagree, retain both and mark the claim REVIEW. Do not average incompatible observations or choose the convenient one. The evaluation owner records what changed, which evidence applies to the current boundary, and what must be rerun. When required evidence is unavailable, the status stays NOT_TESTED.

Run the workflow as a sequence of decisions

The Private AI Brain evidence packet follows this working sequence: source inventory, access classification, parsing, chunking, indexing, retrieval, answer generation, citation checks, evaluation, and refresh. Within this artifact, each phrase marks a state boundary for a local retrieval-augmented knowledge system. A stage output becomes the next named input, while a failed, missing, or unavailable check keeps the dependent evidence packet decision closed.

StepDecision ownerObservable criterionEvidence to retainCounterexample policy
1data ownerSources and access classes are inventoried.Direct observation or test bound to the current artifactRun a safe negative fixture from the separate failure register; do not infer a one-to-one mapping by list position.
2privacy ownerRetrieval permissions match source permissions.Direct observation or test bound to the current artifactRun a safe negative fixture from the separate failure register; do not infer a one-to-one mapping by list position.
3retrieval engineerAnswers cite claim-level evidence.Direct observation or test bound to the current artifactRun a safe negative fixture from the separate failure register; do not infer a one-to-one mapping by list position.
4evaluation ownerDeletion and refresh propagate to the index.Direct observation or test bound to the current artifactRun a safe negative fixture from the separate failure register; do not infer a one-to-one mapping by list position.
5system operatorAdversarial documents are included in tests.Direct observation or test bound to the current artifactRun a safe negative fixture from the separate failure register; do not infer a one-to-one mapping by list position.

Separate failure register

  • FAIL-01: Restricted documents placed in a shared index.
  • FAIL-02: Retrieval evaluated only by answer fluency.
  • FAIL-03: Stale chunks surviving source deletion.
  • FAIL-04: Citations pointing to a relevant page but not the claim.
  • FAIL-05: Prompt injection entering through indexed documents.

The register supplies negative cases for the complete acceptance set. A reviewer determines affected checks from observed evidence; array position never asserts that one failure proves or disproves one criterion.

The producer can explain what it attempted, but the evaluation owner evaluates the evidence. If the artifact changes, its prior verdict expires. This is especially important for a local retrieval-augmented knowledge system, where a plausible narrative can hide a stale configuration, an untested negative case, or an authority mismatch.

Failure and recovery drills

A useful Private AI Brain evidence packet explains what happens when its happy path breaks. These drills come from the accepted product truth record rather than a claim that every buyer has each failure. Use safe synthetic or authorized observations for a local retrieval-augmented knowledge system, and keep private credentials out of every fixture.

1. Restricted documents placed in a shared index.

Detect for Private AI Brain: data owner captures a direct readback or safe fixture that makes this evidence packet condition observable. Its record binds source, time, method, and the current ART-15-02 fingerprint.

Contain the evidence packet: stop only the affected Private AI Brain path after observing “restricted documents placed in a shared index”. Preserve its failed material and last verified state instead of erasing evidence or blindly repeating an external effect.

Recover and prove: apply the smallest authorized Private AI Brain correction, then have a distinct reviewer re-evaluate the complete accepted check set. Do not select one check merely because it shares this failure's list position. If any affected evidence packet check cannot run, its result remains NOT_TESTED.

2. Retrieval evaluated only by answer fluency.

Detect for Private AI Brain: privacy owner captures a direct readback or safe fixture that makes this evidence packet condition observable. Its record binds source, time, method, and the current ART-15-02 fingerprint.

Contain the evidence packet: stop only the affected Private AI Brain path after observing “retrieval evaluated only by answer fluency”. Preserve its failed material and last verified state instead of erasing evidence or blindly repeating an external effect.

Recover and prove: apply the smallest authorized Private AI Brain correction, then have a distinct reviewer re-evaluate the complete accepted check set. Do not select one check merely because it shares this failure's list position. If any affected evidence packet check cannot run, its result remains NOT_TESTED.

3. Stale chunks surviving source deletion.

Detect for Private AI Brain: retrieval engineer captures a direct readback or safe fixture that makes this evidence packet condition observable. Its record binds source, time, method, and the current ART-15-02 fingerprint.

Contain the evidence packet: stop only the affected Private AI Brain path after observing “stale chunks surviving source deletion”. Preserve its failed material and last verified state instead of erasing evidence or blindly repeating an external effect.

Recover and prove: apply the smallest authorized Private AI Brain correction, then have a distinct reviewer re-evaluate the complete accepted check set. Do not select one check merely because it shares this failure's list position. If any affected evidence packet check cannot run, its result remains NOT_TESTED.

4. Citations pointing to a relevant page but not the claim.

Detect for Private AI Brain: evaluation owner captures a direct readback or safe fixture that makes this evidence packet condition observable. Its record binds source, time, method, and the current ART-15-02 fingerprint.

Contain the evidence packet: stop only the affected Private AI Brain path after observing “citations pointing to a relevant page but not the claim”. Preserve its failed material and last verified state instead of erasing evidence or blindly repeating an external effect.

Recover and prove: apply the smallest authorized Private AI Brain correction, then have a distinct reviewer re-evaluate the complete accepted check set. Do not select one check merely because it shares this failure's list position. If any affected evidence packet check cannot run, its result remains NOT_TESTED.

5. Prompt injection entering through indexed documents.

Detect for Private AI Brain: system operator captures a direct readback or safe fixture that makes this evidence packet condition observable. Its record binds source, time, method, and the current ART-15-02 fingerprint.

Contain the evidence packet: stop only the affected Private AI Brain path after observing “prompt injection entering through indexed documents”. Preserve its failed material and last verified state instead of erasing evidence or blindly repeating an external effect.

Recover and prove: apply the smallest authorized Private AI Brain correction, then have a distinct reviewer re-evaluate the complete accepted check set. Do not select one check merely because it shares this failure's list position. If any affected evidence packet check cannot run, its result remains NOT_TESTED.

Ownership and handoff

RoleOwned decisionSeparation rule
data ownerowns the request boundary and confirms the intended consequenceMay not approve evidence it produced when independent review is required
privacy ownerowns the bounded implementation surface and action receiptMay not approve evidence it produced when independent review is required
retrieval engineerowns source material, freshness, and the claim-to-evidence mapMay not approve evidence it produced when independent review is required
evaluation ownerowns release readiness, rollback, and destination verificationMay not approve evidence it produced when independent review is required
system operatorowns the human approval or escalation decisionMay not approve evidence it produced when independent review is required

For this Private AI Brain evidence packet, the adjudication role is evaluation owner. That role judges frozen acceptance evidence for a local retrieval-augmented knowledge system without becoming the product owner, legal adviser, security authority, or buyer. Its handoff retains open gaps, failed evidence, changed hashes, and the next action permitted for ART-15-02.

Evidence and acceptance

Use these product-specific statements as candidate acceptance checks:

  • Sources and access classes are inventoried.
  • Retrieval permissions match source permissions.
  • Answers cite claim-level evidence.
  • Deletion and refresh propagate to the index.
  • Adversarial documents are included in tests.

For every Private AI Brain evidence packet check, retain the tested object, environment or source, observation time, method, expected result, actual result, verifier identity, and artifact hash. In this ART-15-02 record, label a direct readback OBSERVED, a reproducible transformation COMPUTED, and an interpretation JUDGMENT; never merge those states into one confident claim.

The research packet observed 3 impressions across adjacent site queries such as “which of the following statements is true about retrieval” for the exact Search Console property https://sincllm.com/ during 2026-06-02/2026-08-30. Those observations help locate an existing audience vocabulary. They are not search-volume estimates, do not prove demand for this exact page, and do not predict clicks or rankings.

The product boundary remains controlling: Local deployment reduces some egress paths but does not make the data correct, the retrieval complete, or the answer safe. Access control, backups, logs, and operators remain part of the threat model.

Implementation checklist

  • The evidence packet names the distinct reader job: Assemble reviewable evidence for a local retrieval-augmented knowledge system without turning assumptions or producer claims into proof.
  • The input boundary is explicit: approved documents or data exports, access rules, answer use cases, and evaluation examples.
  • The intended deliverable is explicit: a local-model RAG system checked by a QA agent.
  • Every required acceptance check has current evidence or an honest NOT_TESTED status.
  • At least one negative fixture covers restricted documents placed in a shared index.
  • The evaluation owner is distinct from the artifact producer.
  • Rollback or reopen conditions are written before consequential action.
  • No ranking, traffic, conversion, compliance, certification, or buyer-outcome guarantee was added.

When this Private AI Brain evidence packet has a failed item, repair that named item and rerun its dependent checks. Keep the frozen threshold intact; the remaining checks cannot establish that the failed ART-15-02 condition probably holds.

Sources and claim boundaries

For ART-15-02, the sincLLM catalog supplies the Private AI Brain product description. Its third-party references support only the general evidence packet procedure each source addresses. None proves a buyer-specific outcome from Private AI Brain or turns this page into a ranking, citation, or AI-answer guarantee.

Keep the Private AI Brain next step bounded

Review the catalog for this evidence packet, its required inputs, and its limits. Test any buyer-specific outcome from Private AI Brain in the buyer's environment instead of assuming it from the guide.

Explore the sincLLM product catalog