Cedar Cloud Software — fictional records

Completed example with unresolved work. No source documents or customer records are included.

Assessment scope

Scope ID
S-1
Team and contractors
24 employees and 4 contractors across engineering, support and operations
Purpose
An enterprise prospect asks about AI in your company and product.
Review period
October 2026 fictional exercise
Excluded areas and reason
Examples focus on employee AI use. Customer-facing AI features need separate architecture, model evaluation and data-processing evidence.
Accountable owner
Engineering operations lead
Next review
2026-10-22

Coverage

Coverage ID
C-1
Team or source
Staff
People invited
24
Responses received
24
Evidence source
Staff questionnaire
Coverage
Reviewed
Missing information and reason
Responses are disclosures, not technical verification.
Owner
Engineering operations lead
Coverage ID
C-2
Team or source
Contractors and associates
People invited
4
Responses received
2
Evidence source
Contractor questionnaire
Coverage
Partial
Missing information and reason
Two contractors have not confirmed personal assistants or repository connections
Owner
Engineering operations lead

AI uses

Use ID
U-1
Tool or embedded feature
CodeDraft
Account or plan
Company-managed example account
Team / role
Engineering
Business purpose
Generate test ideas for an internal utility
Observed information categories — not permission
Synthetic fixtures and public example code
Permitted information categories
Synthetic fixtures and public example code
Approved use and access conditions
Engineering manager reviews generated code, dependencies and test results before merge
Permission decision reference
Fictional records / Cedar Cloud Software / E-1
Files, connectors and permitted actions
No connectors or external actions in this example
Approval status
Restricted
Owner
Engineering manager
Source reference
Fictional staff disclosure and review note
Evidence confidence
Self-reported
Next review
2026-10-22
Use ID
U-2
Tool or embedded feature
SupportDraft
Account or plan
Account details awaiting review
Team / role
Support
Business purpose
Draft responses from customer support tickets
Observed information categories — not permission
Customer contacts, logs and possible secrets
Permitted information categories
None pending permission review
Approved use and access conditions
Support and security owners confirm permitted fields and retention before use
Permission decision reference
Not recorded
Files, connectors and permitted actions
Not verified
Approval status
Unapproved
Owner
Engineering manager
Source reference
Fictional staff disclosure and review note
Evidence confidence
Self-reported
Next review
2026-10-22
Use ID
U-3
Tool or embedded feature
DocsDraft
Account or plan
Company-managed example account
Team / role
Product
Business purpose
Draft documentation from public product information
Observed information categories — not permission
Published release notes and synthetic examples
Permitted information categories
Published release notes and synthetic examples
Approved use and access conditions
Product owner checks actual behavior and avoids unsupported security or AI claims
Permission decision reference
Fictional records / Cedar Cloud Software / E-1
Files, connectors and permitted actions
No connectors or external actions in this example
Approval status
Restricted
Owner
Engineering manager
Source reference
Fictional staff disclosure and review note
Evidence confidence
Self-reported
Next review
2026-10-22

Exposure review

Risk ID
R-1
Related use ID
U-1
What could go wrong
A suggested dependency still needs provenance and license review
Sensitive or client data
No
Vendor terms checked
Unknown
Client requirements checked
Yes
Agent access
No external actions
Output review
Planned
Safeguards operating today
Engineering manager reviews generated code, dependencies and test results before merge
Reviewer priority
Investigate
Reviewer rationale
Review the stated gap before wider use
Reviewer
Engineering manager
Reviewed on
2026-10-08
Risk ID
R-2
Related use ID
U-2
What could go wrong
Customer-data processing and log redaction are not yet verified
Sensitive or client data
Yes
Vendor terms checked
Unknown
Client requirements checked
Unknown
Agent access
Unknown
Output review
Planned
Safeguards operating today
Support and security owners confirm permitted fields and retention before use
Reviewer priority
Priority
Reviewer rationale
Sensitive client data with unresolved permissions
Reviewer
Engineering manager
Reviewed on
2026-10-08
Risk ID
R-3
Related use ID
U-3
What could go wrong
Two contractors have not confirmed personal assistants or repository connections
Sensitive or client data
No
Vendor terms checked
Unknown
Client requirements checked
Yes
Agent access
No external actions
Output review
Planned
Safeguards operating today
Product owner checks actual behavior and avoids unsupported security or AI claims
Reviewer priority
Investigate
Reviewer rationale
Review the stated gap before wider use
Reviewer
Engineering manager
Reviewed on
2026-10-08

Use decisions

Decision ID
D-1
Related use ID
U-1
Decision
Restrict
Permitted use and conditions
Engineering manager reviews generated code, dependencies and test results before merge
Decision owner
Engineering manager
Decision date
2026-10-08
Decision evidence
Fictional records / Cedar Cloud Software / E-1
Next review
2026-10-22
Decision ID
D-2
Related use ID
U-2
Decision
Escalate
Permitted use and conditions
Pause real-data use until permissions and handling are reviewed.
Decision owner
Engineering manager
Decision date
2026-10-08
Decision evidence
Fictional records / Cedar Cloud Software / E-2
Next review
2026-10-22
Decision ID
D-3
Related use ID
U-3
Decision
Restrict
Permitted use and conditions
Product owner checks actual behavior and avoids unsupported security or AI claims
Decision owner
Engineering manager
Decision date
2026-10-08
Decision evidence
Fictional records / Cedar Cloud Software / E-3
Next review
2026-10-22

Actions

Action ID
A-1
Related use ID
U-1
Action and completion evidence needed
A suggested dependency still needs provenance and license review. Engineering manager reviews generated code, dependencies and test results before merge
Owner
Engineering manager
Due date
2026-10-22
Status
In progress
Completion evidence reference
Follow-up evidence not yet supplied
Action ID
A-2
Related use ID
U-2
Action and completion evidence needed
Customer-data processing and log redaction are not yet verified. Support and security owners confirm permitted fields and retention before use
Owner
Engineering manager
Due date
2026-10-22
Status
Blocked
Completion evidence reference
Follow-up evidence not yet supplied
Action ID
A-3
Related use ID
U-3
Action and completion evidence needed
Two contractors have not confirmed personal assistants or repository connections. Product owner checks actual behavior and avoids unsupported security or AI claims
Owner
Engineering manager
Due date
2026-10-22
Status
In progress
Completion evidence reference
Follow-up evidence not yet supplied

Evidence

Evidence ID
E-1
Related use ID
U-1
What this record supports
Engineering-approved tool and repository scope
Approved repository reference
Fictional records / Cedar Cloud Software / E-1
Owner
Engineering operations lead
Reviewed on
2026-10-08
Scope and limitations
Illustrative reference only; underlying source document is not included.
Evidence ID
E-2
Related use ID
U-2
What this record supports
Reviewed customer-data flow and supplier terms
Approved repository reference
Fictional records / Cedar Cloud Software / E-2
Owner
Engineering operations lead
Reviewed on
2026-10-08
Scope and limitations
Requested; not yet supplied. No permission is established.
Evidence ID
E-3
Related use ID
U-3
What this record supports
Technical answer approval record
Approved repository reference
Fictional records / Cedar Cloud Software / E-3
Owner
Engineering operations lead
Reviewed on
2026-10-08
Scope and limitations
Illustrative reference only; underlying source document is not included.

Imported source records

No records yet. Follow-up remains open.