Action

Action is an atomic business operation, usually over one aggregate.

Generated facts

Layer: domain
Generated path: app/Pulsar/Domain/{Domain}/Actions/{Name}.php
Generator command: make:action
Workflow method: execute()
Stability: Current manifest surface (Pulsar 0.4.1)

Canonical example

Generated src/stubs/action.stub — canonical synchronized stub.

<?php

namespace {{namespace}};

class {{name}}
{
    public function execute()
    {
        //
    }
}

Responsibility

Action owns the responsibility stated above; it must not absorb delivery, transaction, or unrelated cross-layer behavior.

Placement and dependencies

Keep this type in its generated Domain path. Domain is independent of delivery concerns; Infrastructure implements Domain-owned Contracts at its boundary.

Workflow and tests

Action is consumed by the owning Domain or Service workflow and returns a delivery-neutral result. Test its direct contract, its rejected boundary cases, and the caller or callee that proves the rule in application flow.

Three pitfalls

❌ Prohibited: move this responsibility into a neighboring type merely because it is nearby.
✅ Correct: keep the generated placement and depend only on the documented layer direction.
✅ Correct: test the boundary through the caller and the return or side effect visible to its callee.

Boundaries

❌ Prohibited: Do not call a Query, another Action, or emit events from an Action.

✅ Correct: Pass needed data in and let a UseCase or Operation coordinate reads and events.

Action ​