NSI generation turns switch activity into obligations

What the public implementation shows

Guevara models net settlement headers and details, implements NSIGeneratorService, and exposes settlement summary, detail, file, and manual creation queries.

The generator transforms switch-adjacent transaction data into institutionally controlled settlement artifacts. This is the implementation fact behind the note; the architectural reading begins from that visible boundary rather than from an assumed production story.

Operating principleSettlement files are derived financial products whose lineage must remain visible.

The decision behind the mechanism

Header, detail, and file operations are explicit so totals, participant obligations, and distribution can be reconciled.

A spreadsheet produced outside the platform can lose source period, generation version, participant detail, and authorization history. 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.

• Freeze a defined settlement input window.
• Reconcile header totals to participant details.
• Version and identify every generated artifact.
• Control manual creation and download permissions.

How the control should be operated

Every NSI run should identify source window, included records, exclusions, generated totals, artifact hash, creator, and distribution record.

The institution can explain how each participant obligation was produced. 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.