Skip to main content

pack-local-utility pattern

LocalArtifactFlow

Trace a supported artifact from portal session through local browser action to a user-controlled destination.

pack/local-utility · candidate · @sanchika/patterns

Product job

Confirm custody at each stage before allowing a portal response to become a local artifact.

Trace a supported artifact from portal session through local browser action to a user-controlled destination.

Anatomy and required fields

sourceStage

Authenticated source session and credential boundary.

localActionStage

Browser action and network behavior.

destinationStage

User-controlled output location.

stepCustody

Custodian or location, data involved, action, and crossing facts for every stage.

sourceEvidence

Inspectable evidence supporting each custody claim.

resultingArtifact

Result produced by each stage and the final local artifact.

custodyFacts

Credentials, cookies, file, telemetry, and source facts.

artifactReceipt

Filename, destination, source, and release inspection links.

Required fields
  • sourceStage
  • localActionStage
  • destinationStage
  • stepCustody
  • sourceEvidence
  • resultingArtifact
  • custodyFacts
  • artifactReceipt

Default and edge states

ready

The supported local flow can start.

  • source
  • local action
  • destination
running

A local browser action is active.

  • in progress
  • network boundary
  • cancel or wait
complete

A local artifact is available.

  • saved locally
  • filename
  • destination
blocked

The local flow cannot continue safely.

  • blocked
  • reason
  • manual path

Composed synthetic exemplar

Local custody traceFrom portal session to this device.
No ComplyEaze handoff
  1. 01

    GST Portal session

    The user signs in and opens a supported filed return on the government portal.

    Credentials remain on GST Portal
    Custodian / location
    User in the GST Portal browser tab
    Data / action
    Credentials and the selected filed-return request
    Crosses
    The request and response stay within the portal session
    Never crosses
    Credentials or session cookies to ComplyEaze
    Source
    Current supported GST Portal page
    Result
    Supported portal response ready for the browser action
  2. 02

    Pack local browser action

    The extension initiates the supported download inside the user's browser session.

    Session and cookies are not handed to ComplyEaze
    Custodian / location
    User's browser and local Pack extension
    Data / action
    Supported portal response and local download instruction
    Crosses
    A supported request goes only to the GST Portal destination
    Never crosses
    Session cookies, credentials, or file content to ComplyEaze
    Source
    Public Pack source and the active portal response
    Result
    Browser-managed download begins
  3. 03

    Chrome Downloads

    The browser saves the returned file into the user's Downloads on this device.

    File remains user-controlled and local
    Custodian / location
    User on this device in Chrome Downloads
    Data / action
    The supported filed-return artifact
    Crosses
    The file moves from the portal response into local Downloads
    Never crosses
    The downloaded file to ComplyEaze
    Source
    Browser download receipt and public Pack release evidence
    Result
    User-controlled local file
State
Local only · destination: user-controlled Chrome Downloads · no handoff to ComplyEaze
Current custodian
User on this device
What moves
Supported portal response into Chrome Downloads
What never moves
Credentials, session cookies, or downloaded file to ComplyEaze
Credentials / session
Remain in the GST Portal browser session
Local destination
User-controlled Chrome Downloads
Source / release
Public source and selected release remain inspectable
User control
User chooses permission, destination, and later file handling
Local resultsupported-return-example.pdfSynthetic filename · Chrome Downloads
Network destinationGST Portal response onlyNo extension workflow telemetry
Proof availableSource and release inspectable
Claim
Supported portal response to a local file
Source / release
Repository: public Pack source · release artifact selected by consumer
Status / checked
Current synthetic reference · 14 July 2026 · package validator
Reference / limitation
Checksum comes from the selected release artifact; runtime proof is a separate gate

State coverage

Default and consequential edges remain inspectable.

readyThe supported local flow can start.source · local action
runningA local browser action is active.in progress · network boundary
completeA local artifact is available.saved locally · filename
blockedThe local flow cannot continue safely.blocked · reason

Trust, source, and consumer obligations

Trust boundaries
  • 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.
Consumer owns
  • Prove portal behavior, permissions, network requests, downloads, telemetry, release evidence, and every custody statement.
Responsive behavior
  • Stack numbered stages without changing custody order.
  • Keep the artifact receipt and proof links untruncated.
Forced colors and reduced motion
  • 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-local-artifact-flow
Group
pack-local-utility