Least privilege
Access is scoped to what each user, connector, or service actually needs.
KronForge is built around role-aware access, connector boundaries, and approval-aware actions rather than casual broad access.
Security & governance
Governed by least privilege, explicit approvals, and maintainable engineering.
KronForge is designed for real operational work, which means permissions, isolation, changes, and documentation have to be handled deliberately. This page describes the approach, not a certification or legal compliance claim.
Client isolation
Each client environment is isolated.
Data, credentials, context, logs, and operational history are not casually shared across clients. Exact deployment details are agreed by client need.
Explicit approvals
Material changes require the right human approval.
The Brain may assist with analysis, documentation, and proposals. It does not silently self-authorize privileged or production-impacting actions.
Audited changes
Work should be traceable later.
Audit records, documentation, and governed releases are part of the operating model so improvements remain reviewable and supportable.
Maintainable engineering
Custom work still has to be supportable software.
KronForge emphasizes owned boundaries, testing, documentation, recovery paths, and operational discipline instead of opaque automation sprawl.
Approved operating memory
The Wiki is maintained, not dumped into existence.
The operational knowledge base is meant to be trusted and curated, not treated as a raw pile of emails and files.
KronForge does not make unsupported certification or compliance claims on this site. Security, hosting, access, and support details are defined in the client agreement and delivery scope.
Governance matters