What stays local and what remains a draft.
tools-local-artifact pattern
LocalBoundaryBanner
State browser-local storage, account, upload, and review behavior before tool input.
tools/local-artifact · candidate · @sanchika/patternsProduct job
Confirm where work is processed, whether it leaves the browser, and who reviews the output before entering data.
State browser-local storage, account, upload, and review behavior before tool input.
Anatomy and required fields
Browser or device location where work is processed.
Whether an account is required.
Whether entered work leaves the browser.
Named network or telemetry behavior.
Who must review the result.
Inspectable source or policy link.
- boundaryClaim
- processingLocation
- accountFact
- uploadFact
- networkTelemetryFact
- reviewFact
- sourcePolicy
Default and edge states
No upload or account is required.
- browser-local
- no upload
- review named
A later action leaves the local boundary.
- handoff
- destination
- reason
Composed synthetic exemplar
State coverage
Default and consequential edges remain inspectable.
Trust, source, and consumer obligations
- Search terms, entered facts, and draft outputs stay in the browser unless a named adopter action says otherwise.
- Every tool names its input, output, review requirement, and local or external boundary before opening.
- Provide each tool specification, runtime, source mapping, draft generation, export, storage, and any external handoff.
- Stack facts after the claim and before input controls.
- Keep every fact labelled in text.
- Retain text status, result boundaries, native focus, link underlines, and selected filters using system colors.
- Keep directory results, empty state, draft status, and next action understandable without animated filtering or confirmation.
Compact API reference
- Package
@sanchika/patterns- CSS
@sanchika/patterns/styles.css- Base class
sk-pattern-local-boundary-banner- Group
tools-local-artifact