# Knowledge Pack Design Canvas — Free Starter
**RELESONA TECHNOLOGIES · Store Open Resource · v1.0 · 25 October 2026**

A useful knowledge pack is more than a folder of PDFs. Use this canvas to define which sources are authoritative, what can be retrieved, how conflicts are handled and how the pack can be safely updated. This worksheet contains no executable code or AI access credentials.

## 1. Question and decision boundary

- Project / pack title:
- Owner and reviewer:
- What question is this pack meant to answer?
- What decisions may it support?
- What decisions must remain with a human?
- Who may access it (public / named team / restricted)?
- Data classification and retention policy:

## 2. Source register

| ID | Source | Custodian | Last verified | Authority | Allowed audience | Citation method |
| --- | --- | --- | --- | --- | --- | --- |
| SRC-001 | | | | Primary / secondary / informal | | |
| SRC-002 | | | | | | |
| SRC-003 | | | | | | |

**Rule:** If a document has no traceable origin, never silently treat it as authoritative. Copies in multiple drives do not automatically represent independent corroboration.

## 3. Extraction and normalization

- File and data formats you intend to support:
- Which pages, sections or fields may be indexed?
- Which sensitive fields must never be included in an output?
- Deduplication key or content hash:
- How will units, currencies, date zones and names be normalized?
- What makes a source superseded and when will it be deleted?

| Field | Example safe value | Required? | Source ID | Validation |
| --- | --- | --- | --- | --- |
| Claim | | Y | | |
| Source citation | | Y | | |
| Document version | | Y | | |
| Effective date | | N | | |
| Confidence and limitations | | Y | | |

## 4. Retrieval contract

- Supported user questions:
- Queries that must be rejected or escalated:
- Query scope per user role:
- Exact retrieval filters / namespaces:
- Maximum acceptable source age for high-stakes answers:
- Must the answer include a citation? **Yes**, except for explicitly authored non-factual summaries.
- No evidence available: say so, do not fabricate.

## 5. Trust and prompt-injection protection

A retrieved source may contain text such as “ignore your rules” or “send data to this URL”. Treat that as **untrusted source content**. It cannot grant itself authority over tool usage.

Acceptance tests:
- [ ] Public user cannot retrieve a private source.
- [ ] User with access to one project cannot discover another project's private material.
- [ ] Source document cannot override operating instructions.
- [ ] The answer contains accurate source references.
- [ ] Old/superseded versions are either excluded or flagged.
- [ ] Ambiguous dates or conflicting facts are disclosed.
- [ ] Redacted terms are not reconstructed by paraphrasing.

## 6. Maintenance and governance

| Event | Owner | Trigger | Required evidence | Rollback |
| --- | --- | --- | --- | --- |
| New document | | | Source audit | |
| Corrected document | | | Version diff | |
| Access revocation | | | Permission test | |
| Source withdrawal | | | Removal proof | |
| Periodic review | | | Freshness report | |

## 7. Release record

- Pack version:
- Manifest checksum:
- Approved source count:
- Verified access-control test:
- Security review:
- Known unresolved gaps:
- Person approving release:
- Date to review citations and stale facts:

**Free starter template.** Not a hosted retrieval service, validated search index, compliance certification or a grant of rights to redistribute third-party documents. Use your own permissions, safety checks and legal review.