Canonical context
One approved source for durable identity, preferences, career facts, stories, voice, decisions, and evidence.
Product
Context flows. Ownership stays clear.
Holoself is intentionally inspectable: canonical Markdown, explicit links, privacy-aware lenses, local retrieval, source provenance, and review before durable change.
How linked context flows.
Relevant and permitted
A lens selects useful depth and enforces visibility. It never creates a separate persona.
Execution stays local
Project context combines with self context for the task while applications, posts, code, or research remain project-owned.
Project learns something reusable → creates proposal with evidence → you inspect diff → approval updates self with provenance
Resolution order
Enough context—not every context.
1
Load canonical self
Read approved files from profile and context directories. Markdown remains source of truth.
2
Apply selected lens
General, career, publishing, technical, leadership, interview, or private. Visibility and sensitivity metadata restrict access.
3
Add project and task relevance
Independent project files and task terms determine what receives priority. Self files are not copied by default.
4
Return provenance-preserving output
JSON or tool packets include source paths, restrictions, warnings, and pending proposals.
Visibility model
Lenses govern disclosure, not identity.
| Visibility | Purpose | Typical use |
|---|---|---|
private | Only explicit private-lens work | Personal logistics or sensitive reflection |
linked-projects | Reusable across trusted linked projects | Preferences and work style |
career | Career and interview workflows | Achievements and positioning |
publishing | Publishing workflows, still not necessarily public | Voice guidance and draft themes |
public-safe | Explicitly approved for public output | Verified claims and approved stories |
--- visibility: career public_safe: false sensitivity: employer-confidential confidence: confirmed exclude_lenses: - publishing ---
Local retrieval
Indexes accelerate. They do not own truth.
Deterministic index
Project-local JSON records file paths, headings, hashes, freshness, redacted policy metadata, claims, tags, links, and provenance.
Federated search
Search linked self and project indexes in place without centralizing source Markdown.
Safe to rebuild
Indexes are independently versioned, ignorable, and disposable. Secret-like content is excluded.
See it with real workflows.
Career and publishing show why ownership, lenses, evidence, and review matter together.