Audit And Data Controls

WyrdOS should make important operational context reviewable. The current documented controls are strongest around API contracts and evidence proposals.

Evidence Review Trail

External agents should propose candidate evidence instead of directly creating accepted evidence.

The proposal workflow records:

• Target entity type and entity ID.
• Evidence type, title, summary, and source metadata.
• Confidence and reason.
• Approval or rejection.
• Created evidence ID after approval.

Rejected proposals are preserved for review history and do not create accepted evidence.

API-Level Controls

The API uses:

• Bearer API keys.
• Workspace-scoped keys.
• Read, write, and delete permissions.
• Standard error statuses for unauthorized, forbidden, and not found responses.

Use API Keys to set operational rules before exposing API access to scripts or agents.

Data Export

For structured export:

• Use list/get API endpoints for resources.
• Use CLI JSON output for scriptable snapshots.
• Use wyrdos export-context when a full operating context bundle is needed for review or agent work.

Validate exports by checking organisation scope and spot-checking a few source entities in the app.

Data Import

For imports or migrations:

• Start with a small workspace or staging deployment.
• Use write-scoped keys only for the duration of the import.
• Keep a source mapping from external IDs to WyrdOS IDs.
• Import strategy entities before execution entities so containers and zones can link upward.
• Review a sample graph before importing the rest.

Deletion

Some API resources support delete operations. Use delete-scoped keys only for jobs whose purpose is deletion.

Before deletion:

• Export the affected records if rollback matters.
• Confirm workspace and resource IDs.
• Confirm whether linked entities or pages need manual cleanup.
• Run a small test against non-critical data.

Account-level, organisation-level, or compliance-driven deletion requirements should go through Enterprise Handoff.