On your machine
Your configured workspace holds the notes and files. Source reports, revisions, and repair proposals are stored locally. Work endpoints require a local authorized session.
Security
Clear boundaries. Visible limits.
Understand what runs locally, what a connection can transmit, and what the checks can establish.
Across a connection
Connecting a machine lets supported requests and responses pass through the relay. Requested source content can travel to the caller. Choose which tools and machines you make accessible.
Within a check
Evidence checks and source-version checks have different meanings. Neither is a general guarantee that a document, statement, or result is correct.
Read access and write access are separate.
The read and write services use separate credentials. Write actions are gated by the server, and the dashboard renders the write controls the current request is allowed to use. Work and repair endpoints have their own local-only boundary.
Remote-write configuration changes the exposure of supported legacy actions. Consult the configuration documentation before enabling it. A remote connection does not bypass the local-only Work boundary.
Read the technical security modelReview the proposed change, then apply it.
A repair proposal includes its difference, fingerprint, and expiry. Approval refers to that exact proposal. If the proposal or its source conditions are no longer valid, the server refuses the apply operation.
Source reports keep source references and version checks. They are not tamper-proof certifications or independent fact checks.
Security work stays reviewable.
The public documentation describes the implementation boundaries and known limitations. Repository access is currently restricted. This site does not currently offer a public vulnerability-reporting form.