Complete source, release, entitlement, and adapter selection without inventing provider syntax.
The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is cb0703543c8025cdd17cc535. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic.
This source does not establish a complete credential contract. Keep the adapter credential-free until the developer application, runtime, restriction, entitlement, and current authentication generation are approved.
Source, release, account, credential, platform, and lifecycle choices remain explicit.
The exact source guide `mappls-react-native-intouch-sdk` and fingerprint `cb0703543c8025cdd17cc535` recorded in the project
A React Native project with both native build environments
A clean project or adapter module with no inherited Mappls credential or opaque provider state
A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example
A durable aggregate identity, idempotency key, optimistic version, audit, outbox, reconciliation, privacy, and retirement design
Each stage names its proof. Stop when authority is absent; do not borrow adjacent syntax.
Open the repository and README evidence for mappls-react-native-intouch-sdk. Record branch, source fingerprint, maturity, platforms, and the responsible product owner before choosing a package or endpoint.
The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is cb0703543c8025cdd17cc535. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Reconcile public evidence with the issued account and any local correspondence; repository name similarity is not binary or API compatibility proof.
Keep sdk symbols inside one adapter. The application owns bounded inputs, normalized outputs, correlation identity, cancellation, and resource cleanup.
The source contains no copyable fenced example. Stop before provider syntax, obtain the owning contract, then attach its fingerprint and approved sample to this launchpad rather than guessing.
Run creation, observation, transition, retry, unknown-outcome reconciliation, restart recovery, concurrency conflict, event/outbox delivery, privacy, and retirement against the linked journey model.
Repeat the clean build, archive, deploy, or service-start path for the target platform. Verify accessibility, privacy, observability, quota behavior, version rollback, and support evidence before promoting traffic.
The archive is dependency-free, carries no credential value, and makes no provider call. It validates the manifest and gives reviewers the same source and acceptance record.
Download mappls-react-native-intouch-sdk.zip$ npm test
$ node src/inspect.mjs
# 14 files · provider calls 0
# cb0703543c8025cdd17cc5357aff8b04ff3cdb0250d648b5100a4a5fdc2dce69No safe copyable fenced example exists in this snapshot. Obtain the owning contract and approved sample instead of guessing a package, endpoint, callback, or response.
The offline harness remains useful for recording the exact decision and testing the application seam, but it cannot prove provider-specific syntax.
These generated examples bind the exact source slug and fingerprint, normalize failure and lifecycle ownership, and make zero provider calls. They deliberately contain no invented package, endpoint, callback, or response shape.
// Generated from the repository evidence manifest—not provider syntax.
export const sourceContract = Object.freeze({
slug: "mappls-react-native-intouch-sdk",
fingerprint: "cb0703543c8025cdd17cc5357aff8b04ff3cdb0250d648b5100a4a5fdc2dce69",
stateModel: "stateful",
providerCallsEnabled: false,
});
export type BoundaryResult<T> =
| { kind: "ok"; value: T; sourceFingerprint: string }
| { kind: "selection_required" | "denied" | "empty" | "unavailable"; retryable: boolean };
export async function executeBoundary<T>(operation: () => Promise<T>): Promise<BoundaryResult<T>> {
if (!sourceContract.providerCallsEnabled) return { kind: "selection_required", retryable: false };
try {
const value = await operation();
return { kind: "ok", value, sourceFingerprint: sourceContract.fingerprint };
} catch {
return { kind: "unavailable", retryable: true }; // Never persist a credential or private body.
}
}
// Persist command identity before a state-changing adapter call.
export type DurableCommand = { aggregateId: string; idempotencyKey: string; expectedVersion: number };
export function validateCommand(command: DurableCommand) {
if (!command.aggregateId || !command.idempotencyKey || command.expectedVersion < 0) throw new Error("command_invalid");
}Move from reproducible source evidence to a narrow adapter and then a production-qualified lifecycle without upgrading fixture success into a live claim.
A reproducible credential-free evidence record and explicit selection decision.
Run the offline manifest test from a clean checkout.
Compare source slug and SHA-256 fingerprint with the launchpad.
Record product, region, account, entitlement, authentication generation, and release owner—or keep selection blocked.
Manifest tests pass with zero network calls.
No package, endpoint, callback, or response is guessed.
A fixture-tested seam that contains provider-specific types and normalizes all outcomes.
Start with the generated TypeScript and platform-language boundaries.
Add only symbols approved for the selected source revision.
Validate bounded input and output; add cancellation, timeouts, typed failures, and deterministic cleanup.
Application tests run without a provider credential.
Denied, empty, unavailable, stale, duplicate, and cancelled paths are automated.
A production review covering creation, idempotency, observation, transition, unknown outcome, reconciliation, restart, audit, privacy, and retirement.
Exercise every lifecycle and hostile path under the declared state model.
Verify credential restriction, rotation, redaction, quota, privacy, accessibility, and support evidence.
Repeat the clean release build and rollback from a workstation with no hidden local state.
Every transition has an owner, stable identity, observable evidence, and recovery action.
An independent reviewer can reproduce qualification and rollback.
The offline harness validates exact source identity and fingerprint with zero provider calls.
Every copied source example remains sanitized and visibly tied to its repository revision.
Selection-required evidence cannot be promoted to a live-ready package or endpoint.
Success, failure, cancellation, stale result, cleanup, and release proof match the declared state model.
Never log credential values or private provider bodies. Preserve safe identity and reconcile durable operations before retrying them.
A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority.
Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax.
The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line.
Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit.
Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved.
Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence.
Screen, request, controller, subscription, or aggregate generation ownership is missing.
Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content.
The provider may have committed while the application lacks acknowledgement.
Reconcile by stable provider/business identity and original idempotency key; never send a new command identity until authoritative state is known.
Once source selection and the hostile path are proven, continue into a product tutorial or inspect the exact reference.
Open exact reference