ExemptLink
Discuss a pilot
ExemptLink
Home/Controls and data
Authority, provenance and scope

A visible boundary
around every action.

The website shows the approval loop. Production data handling, security assertions and integrations require evidence before they become claims.

Inspect the demo controls Read sample protocol

Research-stage concept · illustrative product preview

EXEMPTLINK / CONTROLS AND DATACONCEPT PREVIEW
A decision has a boundaryRead, suggest and review remain inside the permission boundary; external action is gated.A decision has a boundaryPROPOSED CONTROLS · concept previewReadPermissioned exportsSuggestReviewable evidenceReviewNamed tax ownerExternal actionSeparate approval
Illustrative mobile scene
Read permitted input
Suggest / review
External lane blocked

A decision has a boundary

Plain text control ledger; decorative seam only.

Human review required
DEMO — SYNTHETIC DATAFinite sequence · reviewed states
What exists in this preview

Synthetic input.
Isolated interaction.

Demonstrated in previewProposed for a real pilotNot available here
Fictional sales and certificatesPermissioned historical files for a bounded scopeReal customer/financial uploads
Candidate evidence and source inspectionTax-owner review of actual transaction factsAutomatic legal validity
Scripted corrections and approvalsNamed reviewer authority and append-only historyTax return or GL changes
Approved-but-unsent request stateSeparately approved recipient/script processCustomer emails or external execution
Local illustrative packet downloadValidated retention and immutable packet requirementClaimed production immutability or certifications
Original matte mineral planes separated by a stepped boundary
Human authority

Read. Suggest. Review.
Approve separately.

A source can be read, a relationship suggested and a correction recorded. External action is a different permission—not an automatic next state.

Follow the reviewed loop
Before live evidence

Controls to agree
with the owner.

Data minimization

Purpose and access

Agree permitted fields, users, transfer method and customer PII handling. Public intake needs business context only.

Lifecycle

Retention and deletion

Set a retention period, operational deletion route and evidence required for any completion claim.

View privacy request route
Provenance

Versions and history

Keep original source versions, named decisions, reasons and dated assumptions. A changed packet receives a new version.

Explore packets
Legal responsibility

Selected state and form

Record what the tax owner or counsel must review. No nationwide certificate-validity engine is claimed.

Read source register
Systems and inputs

Historical exports first.

CSV and document inputs are proposed for the initial pilot. No production integrations, encryption posture, hosting region, SSO or security certification is asserted.

Input familyReview requirement
Sales / customer exportEntity mapping, source row and transaction date.
Certificate filesSource/version, named entity, state and received date.
Tax-engine / GL exportsAgreed period, population, currency and cutoff definitions.
CorrespondencePurpose, approved recipients and separate contact permission.
A bounded first step

Start with a sample.
Find out what it adds.

One state. 100 historical exempt sales. One selected workflow. A decision grounded in your tax owner’s review.

Discuss a pilot Proposed pilot · no records required to start