One-sentence custody statement.
pack-local-utility pattern
CustodyBoundary
Summarize who controls credentials, session, artifact, network destination, telemetry, and release proof.
pack/local-utility · candidate · @sanchika/patternsProduct job
Verify who controls each sensitive element, what crosses, what never crosses, and how the user retains control.
Summarize who controls credentials, session, artifact, network destination, telemetry, and release proof.
Anatomy and required fields
Person or system controlling the boundary.
Data, session, and artifact kept inside.
Named destinations or processors outside.
The user-controlled event that crosses the boundary.
Credentials, session, files, or telemetry that never cross.
How the user starts, denies, or stops the crossing.
Named actor and location for each sensitive element.
Observed destination or no-network statement.
Public source and release inspection paths.
- boundaryClaim
- boundaryOwner
- insideBoundary
- outsideBoundary
- crossingEvent
- neverCrosses
- userControl
- custodyFacts
- networkDestination
- sourceProof
Default and edge states
Artifact and workflow data remain user-controlled locally.
- local only
- destination
- no handoff
A named workspace boundary owns the data.
- workspace scoped
- account
- processor
Only named public metadata crosses.
- public metadata
- source
- no private artifact
A user-controlled transfer has not occurred yet.
- transfer pending
- destination
- cancel action
No transfer occurs in the documented flow.
- no transfer
- inside boundary
- evidence
Composed synthetic exemplar
State coverage
Default and consequential edges remain inspectable.
Trust, source, and consumer obligations
- Credentials and portal session remain with the government portal and the user's browser.
- Name any network request, permission, artifact destination, and telemetry behavior before the action.
- Prove portal behavior, permissions, network requests, downloads, telemetry, release evidence, and every custody statement.
- Wrap facts into labelled rows, not unlabeled icons.
- Place unknown or handoff status before the consequential action.
- Retain numbered order, text labels, link underlines, focus, and custody boundaries with system colors.
- Preserve custody order, permission scope, denial behavior, and local destination without animated connectors.
Compact API reference
- Package
@sanchika/patterns- CSS
@sanchika/patterns/styles.css- Base class
sk-pattern-custody-boundary- Group
pack-local-utility