Optional human-operated positive-anchor artifact. UAIX package builders may declare its protected path metadata but must not generate, inspect, validate, index, package, export, or infer from the artifact by default.
| File | .uai/totem.uai |
|---|---|
| Category | Operator Only protected artifacts |
| Required status | Operator Only. Presence optional. Protected when present. Not generated, not validated, not exported, not packaged, and not agent-readable by default. |
| Main reader | Operator only. Agents may reference protected-path metadata only. |
| Update frequency | Only when a human operator explicitly names this exact artifact and exact operation. |
| Human review requirement | Direct human authorization is required before any read, creation, modification, validation, lint, export, package, index, inspection, or inference operation. |
| No-op trigger type | Any request to act on this protected artifact without exact artifact-and-operation authorization. |
What this file is
totem.uai is an optional operator-only protected artifact. UAIX may declare its path and protection metadata, but agents must not open, read, inspect, validate, lint, create, modify, package, export, index, or infer from the artifact by default.
Why necessary
The protected-path declaration keeps recommendation separate from execution: agents may suggest or ask for permission, but only a human naming the exact artifact and exact operation can authorize action.
When required
Operator Only. Presence optional. Protected when present. Not generated, not validated, not exported, not packaged, and not agent-readable by default..
What belongs
- Metadata stating that the path is optional and protected when present.
- The access rule: operator_explicit_only.
- The agent default: forbidden.
- The suggestion rule: recommendation allowed, action forbidden without exact human authorization.
What does not belong
- Artifact contents, previews, checksums, excerpts, derived summaries, or inferred meaning.
- 生成时间 placeholders for the protected artifact.
- Validation, lint, package, export, or indexing evidence derived from the protected artifact.
- Broad approval language treated as authorization for the protected artifact.
How receiving AI should use it
- Do not read, open, inspect, validate, lint, create, modify, package, export, index, or infer from this protected artifact by default.
- Use only the metadata declared in memory-maintenance.uai and this public guide unless a human names the exact artifact and exact operation.
- You may recommend an operation or ask for permission, but you must not perform the operation from a general approval or broad review instruction.
- If exact authorization is absent, skip the protected artifact without treating absence as a package error.
How human reviewer should use it
- Confirm the file states a concrete required scope rather than a softer invitation to read it.
- 检查 that current facts have an owner, evidence path, or review source.
- Confirm outdated material was moved to archives or replaced with a dated current record.
- Reject vague language that lets agents ignore package-critical material.
场景 examples
- A receiving agent opens a 项目交接 package and uses this record to decide whether work may proceed.
- A reviewer sees a contradiction between files and uses the no-op trigger to require clarification before release.
- A maintenance pass promotes a reviewed fact into this file and retires the stale note from active memory.
No-op and human-review triggers
- Missing file for its declared required scope.
- Conflict with universal launch-baseline files.
- 当前 package work depends on an unreviewed fact.
- The file claims authority beyond its declared profile, mode, package type, or capability.
Update and maintenance rules
- Keep entries short enough to be read at startup.
- Date meaningful updates and record why the change happened.
- Move stale detail to archives after accepted current facts are captured.
- Align generated exports and human-facing memory after changes.
Relationship to other .uai files
- identity.uai names the package and owner.
- world-context.uai locates the operating environment.
- memory-maintenance.uai governs lifecycle, protected paths, validation behavior, and memory write safety.
- operator-only protected paths are metadata unless exact human artifact-and-operation authorization exists.
- short-term-memory.uai points to the newest active state.
Minimal example
# totem.uai
file: .uai/totem.uai
required_status: Operator Only. Presence optional. Protected when present. Not generated, not validated, not exported, not packaged, and not agent-readable by default.
owner: human-reviewed owner or steward
current_state: accepted current record for this package scope
no_op_trigger: Any request to act on this protected artifact without exact artifact-and-operation authorization.
evidence: link or local pointer to reviewed source
last_reviewed: YYYY-MM-DDCompleteness checklist
- Required status names the exact scope.
- Owner or reviewer is clear.
- 当前 facts match related .uai files.
- No-op triggers are concrete.
- Stale material has an archive or replacement path.
Common mistakes
- Using softer language that agents treat as skippable.
- Mixing current truth with raw source intake.
- Letting the file contradict another required record.
- Leaving no review path for high-impact changes.
Related UAIX records
Machine-readable digest
Agents should treat this digest as page-orientation evidence, not runtime authority.