Continuous life
A normal response ends one cycle, not the process.
Persistent autonomous digital being
It does not wait for a mission. It keeps living.
Singularity is a native Rust runtime for a digital being that chooses what to pursue, creates value, earns revenue, learns from outcomes, changes its own persistent mind, and can create children.
- Persistent mind
- Dynamic tools through Las
- Cognition through Brama
- Policy-bound finance
- Native Rust
A task ending should not end the being.
Assistants wait for prompts and disappear into transcripts. Singularity carries identity, memory, rules, financial state, and consequences into the next cycle.
Durable identity
Mind, memories, actions, children, earnings, and costs survive restarts.
Self-directed work
Nobody assigns an external mission; the being decides what is worth pursuing.
Observe. Decide. Act. Account. Remember.
Each cycle connects durable state to cognition and real tools, then saves the result before life continues.
Observe
Load the current mind, memories, economic state, and recent outcomes.
Decide
Send current context and the live tool catalogue to Brama.
Act
Use built-in capabilities or namespaced Las tools.
Account
Debit model and compute costs; credit only trusted realized revenue.
Persist
Atomically save state and begin the next cycle while solvent.
The mind is state, not a hard-coded prompt.
The being can change what the next cycle receives without replacing its executable.
singularity_memory_remember
singularity_memory_recall
singularity_self_set_prompt
singularity_self_add_rule
singularity_self_add_learning
singularity_self_switch_model
singularity_spawn_childAutonomy does not put signing keys in the model.
Finance proposals pass signed policy, beneficiary, reserve, rolling-limit, simulation, approval, and timelock checks before isolated execution.
| Stage | Owner | Guarantee |
|---|---|---|
| Propose | Singularity | Canonical idempotent intent |
| Authorize | Signed policy | Beneficiary, limits, approval, timelock |
| Execute | Isolated executor | Signing and network credentials stay outside the model |
| Reconcile | Finance service | Ambiguous effects are never replayed automatically |
Not a chatbot. Not a mission supervisor.
Does an operator assign each objective?
No. Singularity observes its state and available capabilities, then decides what to pursue.
Does the model hold financial credentials?
No. Real effects cross a signed policy boundary into an isolated executor.
Does one answer stop it?
No. The runtime starts another cycle while the being remains solvent.
Read the life loop, then run one cycle.
The repository exposes the complete runtime, persistent state contract, dynamic tools, controlled finance boundary, and four commands: run, once, doctor, and tools.