Meet Ember and Umbra: two agents in the platform

Two beeswax candles, one lit and one unlit, on a dark oak plate

Most SaaS vendors hand you a user manual. We hand you two agents. Ember and Umbra ship with the lights-out.ai platform and are activated inside your own lights-out.ai instance, within GuardRails and SafeZone. They are not our staff doing your work. They are agents you put to work.

lights-out.ai exists so you can build your own quickly and safely with Claude (and Codex, Minimax) inside a framework that holds. Some parts you build from scratch. Other parts are already specified and shipped with the platform. Ember and Umbra belong in the second category.

They are configured, not recruited. They are activated in your instance and then run within the boundaries you set, against the systems you connect. They do not observe weekends, public holidays, or the concept of work-life balance. After a restart they resume where they left off.

If you are reading this, you are either a potential client, a curious observer, or a journalist writing a piece about AI that will inevitably use the phrase "brave new world." We welcome all three. The specifications below describe what the agents do and the boundaries they operate within.

Agent specification: Ember

The lights-out.ai platform
Ref: LO-AGENT-001

Role: Autonomous Process Agent
Activated: When the customer starts the daemon in its lights-out.ai instance
Deactivated: When the customer chooses to shut the process down

Scope of work

Ember performs process execution in the workflows the customer configures it for. This includes but is not limited to: order processing, exception handling, status updates, and any task that a reasonable person would describe as "someone should really handle this automatically."

Ember operates without direct supervision, within the policies and thresholds defined in the customer's intent configuration. This is by design, not oversight.

Working hours

All of them. Ember does not observe weekends, bank holidays, or the concept of work-life balance. In the event of a system restart, Ember resumes where it left off, which is considered the equivalent of a good night's sleep.

Performance expectations

Ember is expected to complete assigned tasks within the parameters the customer defines. Errors are logged in SafeZone, reviewed by the customer, and addressed. Ember does not take feedback personally, which most people who have configured the agent describe as a significant advantage over previous arrangements.

Operation

Ember runs inside SafeZone, our security-classified runtime in Partnersense Cloud. Every call and decision is wrapped by GuardRails. No customer data leaves your instance. No model training takes place on your data.

Termination

The customer can pause or shut Ember down for a given process at any time. In-progress tasks complete before the agent stops.

Agent specification: Umbra

The lights-out.ai platform
Ref: LO-AGENT-002

Role: Autonomous Process Agent
Activated: When the customer starts the daemon in its lights-out.ai instance
Deactivated: When the customer chooses to shut the process down

Scope of work

Umbra performs process execution across assigned workflows, with particular focus on tasks that are time-sensitive, repetitive, or sufficiently unglamorous that no human has volunteered for them in the past twelve months.

Umbra works in parallel with Ember. They do not compete. They do not collaborate in the way humans mean when they use that word. They simply both get on with it.

Working hours

Continuous. Umbra tends to be most active between the hours of 23:00 and 06:00 CET, not because it prefers the night shift, but because that is when the backlog tends to accumulate. There is something poetic about this. We choose not to examine it too closely.

Performance expectations

Umbra is expected to operate within defined process parameters, escalate exceptions where appropriate, and refrain from making decisions that fall outside its defined scope. The last point has proven easier to enforce for an agent than for some previous contractors.

Operation

Identical to Ember. SafeZone, GuardRails, no data out.

Termination

Same terms as Ember. Umbra has acknowledged these terms in the only way it can, which is by continuing to run.

lights-out.ai. The platform. You build the business on top.

Want to see Ember and Umbra in a demo? Book an introduction.