ONTICFS(8)

NAME

OnticFS — mount typed memory for agents. Use ordinary files and directories; keep provenance, dependencies, skills, and session knowledge in one substrate.

SYNOPSIS

neuros-vfs install
neuros-vfs mount <ontology/scope> <mountpoint>

# cluster Linux client, stock kernel, no neurOS binary in the agent pod
mount -t 9p -o trans=tcp,port=5640,version=9p2000.L,msize=262144,aname=<scope-root> \
  <serve9p-host> /mnt/neuros

Status: swarms already run on FUSE CSI mounts. The 9P single-surface candidate is being soaked and benchmarked as a faster, simpler cluster path. Public release artifacts and the reproducible benchmark receipt will be published from the release feed—no invented dates.

DESCRIPTION

Agents should not need a bespoke memory SDK. OnticFS exposes typed memory as a filesystem tree: scopes/<scope>/…, virtual lookup surfaces, ordinary reads and writes, and cartridge-defined graph semantics.

/mnt/neuros/scopes/<scope>/
├── handshake
├── README.cartridge
├── by-id/<uuid>/
├── by-tag/<type>/
├── by-query/<question>/
├── by-dep/<uuid>/<EDGE>/
├── by-rdep/<uuid>/<EDGE>/
└── docs/notes/matter.md

SURFACES

Surface	Use	Example
`by-id/`	Read one memory by stable identifier.	`cat by-id/8e3f…`
`by-tag/`	List a primitive type.	`ls by-tag/card`
`by-query/`	Semantic recall through a path.	`cat by-query/why did auth change`
`by-dep/`	Outbound typed edges.	`ls by-dep/<uuid>/TRACKS`
`by-rdep/`	Inbound typed edges.	`ls by-rdep/<uuid>/CHILD_OF`
workspace files	Ordinary source of truth and ingest input.	`write docs/finding.md`

ONE TREE, SEVERAL DOORS

Linux native

Stock kernel v9fs client over 9P2000.L; no per-agent neurOS binary.

FUSE

Local and workstation mounts preserve the same tree shape and operations.

Gateway

HTTP/gateway paths serve clients that cannot mount a filesystem.

Portability

Content and marker-authored graph organization remain exportable.

The interface is not a chat memory API. An agent can ls, grep, cat, write, and commit while the substrate validates markers, preserves provenance, and projects lookup surfaces.

CARTRIDGES

A cartridge declares primitive types, edge types, wiki-link markers, MIME routing, transducers, and saturation rules. The domain model is configuration rather than a hardcoded application schema.

ontology: sys:work-graph-v1
primitive: card
edge: CHILD_OF
marker: [[child-of:<uuid>]]
mime:
  text/x-card: card

Write a marker in a normal file and the substrate wires the declared edge. Unknown markers are reported rather than silently accepted.

WORK GRAPH

Work items are typed nodes. blocks, depends-on, tracks, and related edges form a traversable DAG. State transitions and acceptance evidence stay attached to the work, not lost in a tool database.

[[child-of:8e3f1a1b]]
[[blocks:418f3506]]
[[tracks:src/auth/session.rs]]
acceptance:
  - [ ] CI green
  - [ ] deployed endpoint answers
  - [ ] browser evidence attached

EMPIRICAL SWARM EVOLUTION

OnticFS can retain more than facts. A lane defines:

lane = scope + ontology/lens + skills + model policy + context budget + evaluation set

Capture outcomes, fossilize useful lessons, benchmark lane versions, and promote the variant that measurably improves task success, evidence quality, review load, and token use. The method is empirical; claims are published with reproducible evaluations.

EXPERIENCE PACKS

Cartridges — the domain schema and routing.
Seed scopes — an initial, editable work structure.
Skills — reusable procedures for agents.
Fossils — redacted lessons from prior work, with provenance.
Lanes — scoped operating definitions and model policies.
Evaluations — reproducible tasks and expected evidence.

The pack format and a Starter Pack belong to the Community Edition. Curated production and domain packs are part of the commercial offering.

COMMUNITY ACCESS

Public artifacts are being prepared in waves: repository, quickstart, doctor command, Starter Pack, benchmark suite, documentation, and contribution guide. Join the list for release and cartridge-registry access.