Kontyr Operations
Deployment, allocation, capital accounts and treasury over recorded milestones and approvals.
What the committee approves and what the operation executes are the same data. There is no second version of the truth to reconcile at close.
Computation lives in the backend and is reproducible: same inputs, same result, with the fingerprint on the record.
Capital deployment
Tracking committed against deployed capital rests on milestones and approvals that are on the record.
Each capital call is tied to its milestone and to the approval that authorised it.
Capital expenditure goes through its approval path before being executed.
Capital allocation
The engine computes allocation scenarios and stores each run with the fingerprint of its inputs. What the surface shows are those results.
Each run is stored with its inputs, so a result can still be explained months later.
The surface describes results; it does not apply allocations nor replace the decision of whoever approves them.
Treasury
Capital accounts and the recorded movements of each vehicle, with their history.
Contributions, distributions and balances recorded per vehicle and investor.
Every entry keeps the document that supports it.
Despliegue de capitalEl despliegue se sigue sobre hitos, llamados de capital y aprobaciones registradas.Recorded tracking
Asignación de capital (VEGA)VEGA calcula y persiste resultados de asignación como salidas de motor, con huella de sus insumos. La superficie pública los describe; no los produce.Computed result · read, not execution
Movimiento de dinero realLos módulos de pagos existen y registran cargos, cobros y conciliación como datos de la operación.Money movement not enabled · requires approval
Every change leaves an audit trail with its author and moment, and engine outputs are stored without overwriting.
Evidencia y trazabilidadCada escritura deja registro de auditoría, y las salidas de motor se guardan sin sobrescribirse, con la huella de sus insumos.Recorded with evidence
