Each requirement must fit the selected prime contract/task order and workstream. The contract defines scope; approved requirements define the behavior to prove. Designated human authorities confirm applicability and approve the baseline.
TASPD source and scope register · reviewed October 11, 2026
Baseline dimension
Current evidence / next verification
Prime / award context
Unissant — historical Vetting Workflow Processing award; selected task order and current assignment require confirmation
Executed Unissant task-order PWS/SOW and modifications are not loaded. The linked 2020 Alliant 2 RFQ covers IT O&M and BISS (70B04C20Q00000131 / 70B04C20Q00000181); its applicability to Unissant’s separately announced vetting/data awards is not established.
Required scope traceability
Prime legal name; contract and task-order IDs; workstream; applicable SOW/PWS version, effective date and section; attachments and modifications; in-scope and out-of-scope disposition.
Required behavior traceability
Approved requirement ID/version and source section; data/schema and business-rule sources; preconditions; expected results; negative paths; test IDs; build/release and execution evidence.
Approval status
Not recorded. Retain reviewer, approving authority, approval date and baseline version. Public discovery and evaluator selection do not grant approval.
Next step: Confirm the applicable contract scope, source versions and approval status with the designated authority. Unresolved scope remains a visible gap.
Synthetic execution examples remain demonstrations and are not approved CBP requirements or actual execution evidence.
Prime scope alignment
Unissant has two separately announced scopes: (1) ATS passenger-vetting application O&M, cloud migration and DevOps enhancements; (2) data/metadata management, analytics, enrichment, storage and discovery.
Application mapping gap: Cargo and shared/enterprise entries remain broader discovery candidates. Their inclusion does not establish delivery responsibility under either Unissant award. Passenger/vetting entries also require individual task-order mapping.
Current disposition: candidate — prime/task-order applicability unverified. Each entry needs the applicable contract/task order, scope section and approved requirement reference before inclusion in an authoritative CRTM.
Data/Metadata: solicitation 70B04C20Q00000179, PWS starts at PDF page 11; Vetting: solicitation 70B04C20Q00000180, PWS starts at PDF page 23. These are procurement scope sources consistent with the separately announced Unissant service areas. Executed-award incorporation, modifications and application-level mapping remain pending.
TASPD · guided walkthrough
Worked example: vetting request validation
Discovery first: source-backed context and SI candidate interpretation, with explicit gaps. The execution lesson that follows is separately synthetic; it is not a discovered CBP requirement or actual run.
Business outcome example: Vetting request handling
Review whether the selected build supports the agreed vetting-request outcome.
Approval status: Public source context only. Applicable contract scope and business expectations require confirmation by the designated authority; no approved requirement baseline is represented.
Open gaps: Authorized scope, approved source material and execution readiness remain to be confirmed.
1. Separate synthetic lesson: establish an invented outcome
DEMO-VET-001: An illustrative request must include a request reference before intake can acknowledge it. No operational vetting decision is modeled. Preconditions: an authorized synthetic test environment, a selected demo build and designated reviewers. This invented rule needs domain SME confirmation before use in a real scope.
2. Prepare candidate tests
Positive input: Request reference: DEMO-VET-100; no person data or targeting rules. Expected: accepted, with one synthetic record. Negative input: Request reference: blank. Expected: rejected, with no accepted record created. Designated reviewers confirm business expectations and assess the evidence. These tests are described here, not generated or executed. Backend/API path: submit valid and missing-reference inputs, verify response and resulting record state. UI path, only if a corresponding screen exists: enter the same values, submit and inspect feedback; correlate with backend evidence. Actual endpoints, selectors and response codes are undiscovered.
3. Select the demo execution context
Build VET-DEMO-B01 · release DEMO-R01 · environment DEMO-QA. The displayed execution is synthetic. Missing environment prerequisites would yield BLOCKED; execution/configuration exceptions would yield NOT_PROVEN. Neither means a confirmed business failure.
4. Inspect a synthetic failure
Illustrative negative-test result: expected rejection, observed acceptance and one synthetic record created. Verdict: DISPROVEN. Evidence reference: DEMO-VET-001-E01, a narrated example rather than an attached log or actual run. This business failure opens a finding; it does not establish release readiness.
5. Track correction and retest
Illustrative finding DEMO-VET-001-F01: required reference was not enforced. Review owner: designated application team, pending assignment. Proposed correction: enforce the approved validation. A correction alone does not close the finding. Rerun both tests against VET-DEMO-B02 · DEMO-R02; synthetic observations now match both expectations. The example is PROVEN only for this narrow stated rule; no live execution is claimed.
6. Review and decide
HI reviews the business baseline, exact build, positive and negative results, evidence and finding disposition. In this illustration, matching retest results could support closure after review. No reviewer approval, finding closure or release decision is actually recorded. PROVEN for one rule does not prove the entire application.
7. Scope a real pilot
Agree on one business outcome, authorized source material, a real build, test environment, data and reviewers. Confirm acceptance criteria and effort baseline. A configured pilot must supply the actual tests, execution evidence and human dispositions that this teaching example does not contain.
Unissant’s 2020 announcements describe CBP vetting support and data services. These historical awards establish context, not your current assignment.
Vetting support includes ATS passenger applications, maintenance, cloud transition and DevOps. Data services includes analytics, metadata, enrichment, storage and discovery.
Choose your application or capability
Choose the project scope first, then filter its applications or workstreams below.
SI assembled this candidate inventory from public TASPD material. HI confirms the applicable workstream: select your area, correct names or add a missing one. This is not a verified current Unissant roster.
Explore a workstream, review its categories, then choose Add to my scope. Selected cards are highlighted; selections remain available when you filter or return.
Tell us where testing fits
Selections stay in this page’s memory. Nothing is submitted automatically. No project assessment or proof run is performed.
Your scope confirmation
Share this summary with AN8 LLC through your usual channel. After confirmation, AN8 PROOF can prepare workstream-specific requirements, proof scenarios and measurable pilot criteria.
