Manual settlement actions need stronger evidence

What the public implementation shows

Guevara contains a CreateManualNSICommand alongside automated NSI monitoring, generation, file queries, and download records.

The manual command uses the same controlled settlement domain instead of asking operators to construct artifacts outside the platform. This is the implementation fact behind the note; the architectural reading begins from that visible boundary rather than from an assumed production story.

Operating principleManual capability is not the absence of control; it requires a more explicit control record.

The decision behind the mechanism

Keeping the exception path inside the system allows permissions, validation, artifact identity, and history to remain intact.

An external spreadsheet workaround may solve an urgent deadline while losing repeatability, review, and evidence of the values submitted. The mechanism matters because it gives that failure a named boundary, durable evidence, and a controlled response instead of leaving the outcome to timing or operator guesswork.

• Use a dedicated permission for manual creation.
• Require an explicit reason and source window.
• Run the same financial validations as automation.
• Mark and audit the resulting artifact as manual.

How the control should be operated

Manual creation should require reason, actor, approved source period, input evidence, validation results, review, and a visible manual classification.

Operational recovery remains possible without pretending the exception was an automated run. The reusable lesson is not to copy a class or endpoint in isolation, but to preserve the relationship between identity, state, authority, evidence, and operational ownership.