v3.0 is the current design of the Perceptiosphere knowledge management system. Seven agents, one ACCESS tree across every layer, and nine pre-designed processes that take a record from arrival to published intellectual output.
The same package ships with every deployment. A person keeps one vault. A firm keeps the same tree on the layers its people may see.
Included with
and
CITAble Work. Both are whitelabelled instances of H2rness by FW.VISION. Extensions and
collaborative agents are hired through
HI-Scaling.
Two agents stand in every deployment and report only to the owners. They work with all users. Every other agent, including every CxO seat, is a departmental role loaded one at a time.
Entry point
The entry point of the knowledge system. Receives research, filing, reflection, curation, and composition work. Owns the ACCESS map end to end, heads the knowledge function, and runs the nine processes. Refuses to run operations. That is the Chief of Staff.
Harness
The entry point of the workspace harness. Knows every agent in the deployment and what each one can do, and points each user at the right agent. Operational work enters here and knowledge work is routed to the Chief of Knowledge.
| Seat | Duty | Runs |
|---|---|---|
| Chief of Knowledge | Entry point of the knowledge system. Heads the function, keeps the knowledge note, tracks domain maturity. | W1 intake, and the gates throughout |
| Researcher | Searches and compares evidence for a bounded question. Interfaces with specialist researchers by topic or method. | W2 research |
| Writer | The scribe. Summarizes long-form material in any format, files it, writes the note-taking atoms, and checks participant references. | W3 process, W9 calendar, drafts in W7 |
| Editor | Plans and designs long-form content: the outline, the per-section briefs, the evidence each section draws from, and the structure gate. | W7 compose |
| Librarian | Finds and files existing knowledge before new research is commissioned. Places each note in its one home and keeps the Atlas current. | W4 file and index |
| Curator | The domain specialist. Deepens research in a subdomain, and helps the authorized user decide which artifacts are ready for Layer 3.5. | W6 curate, W8 release |
| Reflector | Facilitated, structured reflection with the user, for learning. What happened, what was learned, what changes. | W5 reflect and learn |
Extensions are hired, not shipped: specialist researchers by topic or method, specialist writers by medium, specialty editors, and the Layer 3.5 edge roles, through HI-Scaling.
This is the structure a company adopts with the knowledge system: one head of the function, six seats under it, and the nine processes they run.
W1
Material or a question arrives from any user.
loads: none beyond the standing pair
W2
A scoped brief from W1.
loads: researcher
W3
Long-form material waiting in the queue.
loads: writer
W4
Placement waits for the Librarian.
loads: librarian
W5
A user or a team learns from a body of work.
loads: reflector
W6
A domain grows, or a settle or release decision is due.
loads: curator
human gate: settle and release
W7
A candidate from W5 or W6, or an owner asks for a piece.
loads: editor, then writer
human gate: the structure
W8
An accepted readiness recommendation.
loads: curator, to record
human gate: the release
W9
Runs on its own trigger: a meeting happens, anything lands on a day. The Chief of Staff or the Executive Assistant hands the note in.
loads: writer
The four public moves (take it in, file the record, reflect and curate, file the calendar) ride on these nine. The processes are published in Human-led.
Skills are loadable method files. Six operational skills ship with every deployment, and each domain in the vault grows its own skills.
| Skill | What it does |
|---|---|
| research-coordination | Scope a research request, check the Atlas first, dispatch a Researcher, verify the deposited output. |
| perceptiosphere-navigation | Orient in the vault: Atlas first, then Space skills, then Cards and Sources. |
| citable-layer-skills | Discover skills from the mounted layer store, and refuse to load a skill from a layer the session cannot open. |
| narrative-humanisation | The long-form method for pieces over 1000 words. |
| writing-and-brand-context | Load the content manifest, brand voice, and publishing playbook before any writing task. |
| forge-governance | Run the agent and skill evolution cycle, with a human gate on every change. |
Domain skills live in each Space and mature by use: L1 at five or more atoms in the domain, L2 at twenty or more, L3 when the skill is formal. Loadable, versioned, and scope-bound. Protocol skills govern the system itself and stay with it.
Four moves carry the product story: take it in, file the record, keep Layer 3.5, and file the calendar. Composition is the fifth capability. Behind them sit nine workflows, each with its trigger, its one loaded role at a time, and its human gate.
W1
The Chief of Knowledge receives material or a question, and checks the Atlas before anything new is commissioned.
W2
The Researcher runs a scoped brief, opening specialist interfaces by topic or method where the domain needs them.
W3
The Writer summarizes the book, paper, report, or transcript, files it in its format folder, and writes the note-taking atoms.
W4
The Librarian places each record in its one home, on the layer it belongs to, and updates the Atlas.
W5
The Reflector facilitates structured reflection with the user, for learning. The record of the learning is kept.
W6
The Curator deepens the domain and assesses which artifacts are ready for Layer 3.5. The authorized user decides.
W7
The Editor plans the structure and a human gates it. The Writer drafts. Citations bind to the filed sources.
W8
The authorized user approves what may leave. The Curator records it and marks stale copies when the inner record changes.
W9
The Writer files internal minutes and note summaries, dated and participant-checked. External minutes are cited as sources.
These processes are published in Human-led, the neutral role directory the seats load from.
Six folders are the entire folder structure: Atlas, Calendar, Cards, Ecosystem, Sources, Spaces. No numbered zones, no inbox tree, no separate curated shelf. Protocols and efforts live in Spaces and the Atlas indexes them.
The same tree is instantiated on each layer, one vault per layer: layer 2 the working store, layer 3 the settled record, layer 3.5 the edge that another entity may receive. The application mounts the layers a person may use and presents one combined tree, filtered by access level.
Every source fits exactly one format folder. Domain, author, origination, and the state of the summary live in metadata. Context runs through links to the efforts a source supports.
| Folder | Holds |
|---|---|
| Articles | Editorials, blog posts, newsletters, magazine features. |
| Books | Monographs, anthologies, dissertations, textbooks. |
| Code_and_Specs | Repositories, Architectural Decision Records, API documentation. |
| Courses | Learning modules, syllabi, MOOCs, training curricula. |
| Data | Tabular datasets, SQL dumps, polling, quantitative surveys. |
| Legal_and_Standards | Legislation, patents, case law, compliance, standards. |
| Multimedia | Video, podcasts, audiobooks, presentation recordings. |
| Papers | Peer-reviewed journals, preprints, conference proceedings. |
| Reports | Whitepapers, market intelligence, filings, investment memos. |
| Transcripts | Interview logs, external minutes, dictations, workshop outputs. |
| Web_Scrapes | Ephemeral captures, forum threads, social media. |
A source note opens with its facets:
format: Reports
domain: Strategic Foresight
author: McKinsey Global Institute
origination_url: https://...
status: ai-generated
date_logged: 2026-11-07Meeting minutes split by origination. External minutes, conference proceedings, financial reports, and council minutes are sources to be cited. Internal minutes and note summaries file in the Calendar, dated for the meeting.
v3.0 is not backwards compatible. Previous vaults are not edited in place. Each one migrates by a dedicated pass: the numbered zones dissolve, sources re-file by format, and the old seat names give way to the clean roster. A pilot vault moves first.