A proposal comes before the change
The web app, CLI and connected agents prepare proposals against the same API. Review the inputs, before-and-after effect, source evidence and required authority. Preparing a proposal does not execute it.
| Action | Required review |
|---|---|
| Create a holder, link a representative or reply to a holder request | Human confirmation by an authorized administrator or owner |
| Correct a holder profile, issue or transfer shares, or amend instrument terms | Human passkey approval and any required consent |
| Change company access, invite a member or create an API key | Owner passkey approval |
| Create or amend a share class, close a round or execute a conversion | Passkey approval plus the required board consent |
The proposal shows the applicable rule. A company’s consent policy may add board requirements. Preparing consent does not replace the actual approval or evidence required by the company’s governing documents.
Check the exact record
For a correction, compare the previous and replacement values and read the reason. For an issuance, check the holder, instrument, quantity, dates, terms and source. For access changes, check exactly who gains access and to which holder or documents.
A holder profile correction must concern the same legal holder. A different legal owner requires a transfer. Corrections preserve the previous values and require holder export facts to be reviewed again.
When a proposal becomes stale
Approval is bound to the proposal version and content. If the underlying register, policy or a referenced revision changes, the API requires a fresh review or a new proposal. It does not silently approve the replacement. Reject a proposal with a reason when it should not proceed.
What agents can do
An agent or API key may read authorized records and prepare proposals. It cannot approve, sign documents or grant itself access. The human approval surface is separate from the tools available to the model.