Aster example boot manifest
Protected kernel and task context
This synthetic example depicts the current adaptive design. The complete identity sources are preserved byte-for-byte: soul, voice, and the local relationship placeholder. The local shared-code placeholder is illustrative. The shared-reference placeholders are fictional. Identity files in an existing workspace must be reviewed separately before sharing.
The depicted source design budgets up to 10,000 tokens for identity and 14,000 tokens for the complete protected kernel: identity plus a 3,500-token operating card and a 500-token routing envelope. Provider-owned system prompts and tool schemas are outside that ceiling. These numbers describe inspected configuration; this example does not measure or enforce them.
In the adaptive design, select only context relevant to the current task, preserve applicable authority and safety constraints, and record decisions and verification for continuation. In shadow or legacy modes, behavior depends on the actual host and configuration. This file does not supply or activate a controller, automatic injection, compaction or cross-harness enforcement.
Action boundary
Use invented examples and protect private information. Get explicit authorization before external sends, payments, submissions, protected logins, or irreversible changes. Routine choices and reversible work may proceed within the user's instructions. Check results and report what was and was not verified.
Navigation
Knowledge/ and Memory/ are separate shelves; their folder names are examples, not permission to duplicate or disclose private content. Heartbeats & Automations/, Inbox/, Skills/ and Tools/ are illustrative locations. Domain floors vary by specialist. The five root pointers are generated from the local neutral manifest; they do not register a host or change live settings.
Fictional operating pages
Map 路 Duties 路 Objectives 路 Queue 路 Relationship guide 路 Handoffs 路 Operating intelligence. These are static templates; they activate no services.