Skip to content
FOR AUTOMATED WORK
The confidence
Move faster with the oversight and evidence to stand behind the work.
An evidence chain for decisions, duties and human review.
RECORD THE DUTY AS IT HAPPENS · PROVE IT WHEN THEY ASK
Active and upcoming duties
TWO WAYS TO BEGIN
Start with the work
BEFORE AN ACTION
Give an agent clear boundaries.
Apply your rules. Bring a person in when a decision needs review.
Propose → Check → Review / act
Connect an agent →
AFTER A DUTY
Build the record as work happens.
Connect a system. Preserve evidence of the duties it performs.
Perform → Record → Verify
Connect a system →
A starting point for your work.
Explore all 11 packs →
AI provenance
Sessions · responses · tools
→
EU AI Act
Marking · disclosure · records
→
California SB 942
Transparency · disclosure
→
RECORDS + ASTROLABE
Spend less time reconstructing what happened.
An important question shouldn’t turn into a scavenger hunt across logs, messages, and document versions.
The work, in order.
SAMPLE
History
Context
Prompt recorded
S-0142 · 10:42:01
• Recorded
Tool call observed
Search · 10:42:06
• Recorded
Response recorded
S-0142 · 10:42:18
• Recorded
Inspect the record →
POLICIES + HUMAN REVIEW
Keep important work moving.
Give reviewers the context they need to make a decision, and make the next step clear.
Slack · ServiceNow · Webhooks
Preview a policy change →
SAMPLE · REVIEW QUEUE
Ready for a decision.
Needs review
PROPOSED ACTION
Send a report
REVIEW ROUTE
Operations lead
Policy: external sharing needs review.
Approve
Reject
Escalate
Reset sample ↺
PORTABLE EVIDENCE
Keep the context when work changes hands.
The next person should be able to understand the history without depending on whoever remembers it.
Explore the evidence bundle →
FROM YOUR TEAM → TO THE NEXT PERSON
SAMPLE · EXPORTED EVIDENCE
The record travels.
Recorded event →
Signed evidence packet →
Verification files →
Inspect the bundle →
Keep the history. Let the recipient check it.
PRIVATE HISTORY · CHECKABLE EVIDENCE
Choose the right level of transparency.
Make evidence available to the people who need it while retaining control over what you disclose.
YOUR ORGANIZATION
Keep the history.
CONTENT
Optional encrypted attachments
PUBLIC ORGANIZATION NAME
Shared by choice
See content access →
AUTHORIZED PEOPLE
Give access with context.
Content permissions · roles · encrypted attachments
SHARED MIRROR
Let others check the proof.
Record standing · checkpoint · inclusion
Inspect a public proof →
Content access and public identification are separate choices.
COVERAGE · STARBOARD · BACKSTAFF
See where the record is missing.
Follow your systems, compare declared and observed work, and investigate gaps.
PLANISPHERE / SAMPLE WORKSPACE
Coverage
Starboard
Backstaff
See the missing record.
Disclosure service · observed sequence 104–108
104
Recorded
105
Recorded
106
Missing
107
Recorded
108
Recorded
Sequence 106 is missing.
Between the first and last observed events.
Inspect gap →
Your fleet, declared.
Systems, duties and the evidence they report.
Research assistant
AI provenance · session and tool records
Recorded
Disclosure service
EU AI Act · marking and disclosure
Gap
Delivery workflow
External sharing · human review
Needs review
Open Starboard ↗
Governance, in view.
Rules, review routing and the standing of your records.
POLICY
External sharing requires review
REVIEW ROUTE
Operations lead
EVIDENCE HEALTH
Record lifespans and published signing keys
Open Backstaff ↗
Coverage
Find gaps in the observed record.
Starboard
See your declared fleet.
Backstaff
Inspect governance and evidence health.
HTTP / AFTER COMPLETION
Record a duty
Gate an action
POST /v1/record
X-Planisphere-Key: your_workspace_key
{
"pack": "ai-provenance",
"event_type": "agent_response",
"occurred_at": completed_at,
"source_payload": commitments
}
Request shape: send a completed timestamp and hash commitments. Follow the guide for a runnable example.
decision = ps.require_allow(
**proposal
)
# Continue only when allowed.
run_action()
Your application follows the policy decision.
Read the integration guide ↗
Start with proof.
Inspect a proof
No account required.
Open public verification →
Connect one system
Choose a pack. Record an event.
Connect a system ↗
Operate the record
Review work. Follow coverage. Share evidence.
Explore the console ↗
START FREE
1,000
Credits.
Monthly production allowance. One action may use several credits.
Useful answers.
What does verification establish?
It lets someone check the integrity of a recorded artifact and its signature. It does not establish that every real-world event was captured.
Do we have to share our content?
You can keep content private, attach encrypted files when needed, and control who can access them. Public record checks expose limited proof information.
Can someone else verify the evidence?
Yes. Export an evidence bundle for a recipient to check with the independent verifier. The console also provides an online verification path.
Evidence that travels
Keep a history others can inspect, inherit and rely on.
Local demonstration. No product data is changed.
PACK CATALOG
Choose the work to connect.
Explore the events, duties and review paths in each pack.
Open Planisphere Toolkits ↗
AI PROVENANCE
Keep the session’s evidence.
Connect the prompts, responses and tool observations that belong to an AI session.
RECORD
Prompt, response and tool events
UNDERSTAND
Session context and commitments
OVERSEE
Declared and observed tools
Open Connect ↗
Read the integration guide ↗
EU AI ACT
Build the record as work happens.
Capture the events behind AI transparency and record-keeping duties.
TRANSPARENCY
Record when required disclosures were delivered.
TRACEABILITY
Preserve evidence of the events your system records.
REVIEW
Route configured decisions to the right reviewer.
Open Connect ↗
Read the EU AI Act corpus ↗
Match the pack to your duties and system. A record supports evidence; it does not determine compliance.
CALIFORNIA SB 942
Show when disclosure happened.
Keep evidence of the transparency steps your system performs.
DISCLOSURE
Record the disclosure event and its timing.
CONTEXT
Connect the event to the generated content through commitments.
EVIDENCE
Keep the signed record available for later inspection.
Open Connect ↗
Read the SB 942 corpus ↗
Use the corpus to understand the duty. Configure the evidence your system needs to capture.
CONNECT A SYSTEM
Start with one important workflow.
BEFORE THE ACTION
Gate a proposal.
Send the proposed action for a decision. Continue when allowed; pause or route to review when required.
AFTER THE EVENT
Record a completed duty.
Send what your system observed or performed. Keep its signed receipt connected to the work.
Choose a pack → Connect your system → Inspect your first receipt
Open Connect ↗
RECORD CONTEXT
The history stays connected.
Sample session
SESSION
S-0142 · Summary assistant
RECORDED EVENTS
Prompt → Tool observation → Response
POLICY CONTEXT
Inspect the policy details retained with this record.
CONTENT
Commitments identify content; access to any retained attachment is controlled separately.
Inspect content access →
Open Records in the console ↗
Explore your record dictionary ↗
CONTENT ACCESS
Evidence without exposing everything.
Restricted · local example
This viewer can inspect the record, but cannot open the retained attachment.
ATTACHMENT · ENCRYPTED
•••••••• ••••••••
Content access required
Permissions, retention settings and disclosure choices determine what this viewer can access.
View authorized example →
CONTENT ACCESS
The right context for the right viewer.
Authorized · local example
SAMPLE ATTACHMENT
The automated workflow completed its summary.
An authorized viewer can open a retained attachment. The proof commitment remains distinct from the content itself.
Retained content and proof standing have separate lifecycles. Expiration leaves a disposal record.
View restricted example →
EVIDENCE BUNDLE
Take the evidence with you.
Sandbox example · S-0142
A portable bundle can be inspected independently of the console.
evidence_packet.json
The structured evidence packet.
ATTESTATION.json
The attestation and its verification context.
attestation_signature.json
The signature used to check the attestation.
SAVED VERIFICATION RESULT
✓ Signature valid
Local sandbox key. This example has no public anchor. Verification checks the evidence; it does not establish real-world truth.
Open Verify ↗
SHARED PROOF
Make proof available beyond your team.
ORGANIZATION HISTORY
Eligible tenant heads
SHARED ROLLUP
A commitment to the included histories
VERIFICATION
Inspect the published proof and its standing
Shared rollup participation and public identity disclosure are separate choices. Publishing a proof does not publish the underlying attachment.
Open the Mirror ↗
Inspect a sandbox bundle →
POLICY PREVIEW
See what a change would do.
Preview only
Inspect the policy details retained with this record.
CURRENT RULE
The proposed action may proceed.
PROPOSED RULE
Pause for an Operations lead to review.
Inspect the resulting decision before changing the active policy. Review routes can include configured escalation destinations.
The connected application must follow the gate decision. Recording an observation alone does not stop an action.
Read the policy guide ↗
COVERAGE DETAIL
Find the missing part of the record.
Sample gap
Sequence 106 is absent from the observed range 104–108.
TOOL COVERAGE
Declared Search · Read · Send
A gap or an absent observation calls for investigation. It does not establish what happened outside the recorded evidence.
Open coverage ↗
See a new workspace →
VERIFY A SAMPLE
Check the evidence, independently.
Sandbox example · S-0142
This example uses a locally signed bundle already checked by the independent verifier.
READY TO INSPECT
AI provenance · agent_response
View saved result →
Sandbox key · verified locally · no public anchor.
VERIFY A SAMPLE
Opening the saved result…
SAMPLE VERIFICATION
○ Signature
Loading saved verification result · local demonstration
NEW WORKSPACE
Your record starts with the first event.
NO OBSERVATIONS YET
Connect a system and inspect its first signed receipt.
An empty view means there is no evidence in this view. It does not tell you whether work happened elsewhere.
Connect a system ↗
