NASS Contracts - Naflows/naflows-auth GitHub Wiki
NASS Contracts
About
Contracts
NASS Contracts are a secure contractual system between the NASS core and its connected APIs—whether those are part of Naflows, paid plans, or free plans.
These contracts serve as a formal, secure agreement that defines how the central components of NASS communicate with connected APIs. They are most often used to authorize sensitive actions such as:
- Token generation requests
- Administrative actions for system management
Key Differences from Sessions or Tokens
Unlike standard sessions or tokens, NASS Contracts:
- Can be viewed, edited, or terminated at any time by the administrators of any connected API.
- Give administrators ongoing control over their systems, helping prevent malicious or unexpected actions.
This flexibility allows admins to respond quickly to changes, mitigate risks, and maintain secure, intentional system behavior.
Data Retention & Management
NASS never deletes contracts from its own records. This ensures a complete history of all actions authorized through the system. On the API side, administrators can:
- Store contracts for reference
- Delete them (though deletion of active contracts is discouraged)
- Free up storage on their own systems without losing traceability
Because the NASS always retains its own secure record, administrators can safely manage local data storage without compromising accountability or security.