Posture
Observant, not autonomous
Models are expected to inspect context, use tools, and surface their reasoning. Jaguar treats good tool use and memory activation as observable behavior, not magic.
Wanatux OS
Jaguar is the operating posture behind the lab.
Jaguar is the human-in-the-loop layer that gives Wanatux OS its shape: persistent memory, approval-gated actions, and audit trails that let different models work inside the same environment without pretending autonomy they do not have.
Orientation
What Jaguar actually is
Jaguar is the operating stance that keeps the system useful without turning it into a black box. It narrows the contract between human, model, memory, and tools.
Boundary
Action stays gated
Mutations are guarded behind confirm and dry-run paths. The system helps propose, stage, and explain work, but it does not erase operator judgment.
Role
A lab surface, not a product brochure
Jaguar is the public-facing description of a personal operating environment. It exists to explain the system honestly, not to market a fictional platform.
Jaguar is where the system holds its line: memory is external,
actions are reviewable, and models are evaluated by how they behave under
real constraints.
Execution model
How the posture works in practice
The loop is simple: retrieve context, propose a move, approve explicitly, then record what happened so the next session starts from a stronger place.
01
Sense
Models query the environment first: memory, tools, data stores, and prior runs.
02
Propose
They stage a next action instead of improvising from memory alone.
03
Approve
Writes and destructive work stay behind explicit operator approval gates.
04
Record
Results, decisions, and corrections are written back for future recall and audit.
Shared memory
Context lives outside the model
Jaguar treats context as infrastructure. Retrieval spans live session artifacts and long-term knowledge so models can look things up rather than reconstruct them unreliably.
- Knowledge search
- Devloop memory
- Cross-model recall
Approval boundary
Useful assistance without silent execution
The system can stage calendar actions, todo updates, file operations, and maintenance flows, but Jaguar keeps the decision boundary visible.
- confirm=true
- dry-run first
- Audit logging
Live now
Current capabilities in the environment
These are not roadmap claims. They are already running surfaces inside the lab and they are the reason Jaguar is worth naming at all.
Memory
Unified recall across episodic and long-term stores
Memory recall spans live devloop artifacts and indexed knowledge so models can recover prior decisions, documents, and state snapshots in one pass.
Tasks
Todo and calendar automation with visible gates
Due-dated tasks can be reviewed, staged, mirrored into Google Calendar, and audited without collapsing the approval boundary.
Monitoring
Digest and health-check loops
The environment already runs daily quick-wins summaries, Sigil health checks, and other operational observers that keep the system from going stale.
Comparison
Multiple models, one audited operating surface
GPT, Claude, and local models can work against the same memory and tool layer, which makes behavior comparable instead of anecdotal.
Evidence surface
Where Jaguar connects to the rest of the public record
Jaguar is the house. The Sigil page, project surface, and OSF research record are the proof that the house is being used for real work.
Protocol results
Ayala Sigil
The Sigil page shows the measurable side of the epistemic layer: observed model behavior, logging adoption, and structured recall.
Open Sigil →Research artifact
OSF publication trail
The public paper and appendix components provide the formal research frame for the same environment described here.
Read the record →Code surface
Published projects
Selected tools and servers from the lab are published with sanitized configs and working documentation.
View projects →Why the name
What Jaguar represents
Quiet authority.
Jaguar marks the shift from scattered experimentation to deliberate authorship. The system does not need to look loud to hold its boundary. It just needs to remain coherent under pressure.