Workforce Readiness Partner Pilot SOW

This document describes the scope, deliverables, responsibilities, and acceptance criteria for the AI Security Workforce Readiness Partner Pilot engagement. Final binding terms are set in the executed SOW.

1. Pilot Objective

The Partner Pilot establishes whether AI Security Workforce Readiness is a fit for Partner's platform by delivering a concrete, scoped content package and integration architecture specification — sufficient to evaluate the Platform Integration engagement and execute the Annual Content License.

By the end of the Pilot, Partner will have:

• A concrete content sample (role framework, 100-item assessment pack, question subset, learner/cohort outputs, and pathway/lab map) in generic partner-safe JSON/CSV
• An integration architecture spec for each of the three platform surfaces (practitioner, certification, enterprise), specifying the integration seam, data flow, and content schema
• A commercial package — Content License Agreement summary, Platform Integration Order Form draft, and next-phase options — ready for internal review

2. Scope

In scope

Content delivery

• Role framework: multiple AI security role profiles including Agent Security Engineer, AI Product Security Engineer, AI Red Team Engineer, AI Governance Evidence Lead, and broad AI Security Engineer
• Q&A bank: 100 active/review-active items from the canonical AI Security Engineering practice form, with coverage manifest
• Delivery format: JSON + CSV for role framework, question subset, learner result, cohort result, pathway, and manifest
• Scoring fixtures: 5+ synthetic learners scored by the deterministic scoring engine
• Cohort output: aggregate-only cohort calculated from scored learner fixtures, not manually injected percentages
• Integration architecture spec: mapping of content to each of Partner's agreed platform surfaces

Integration architecture specification

• Practitioner dashboard surface: skill-to-role matching schema, job-market data layer feed spec, rendering guidance
• Certification surface: Q&A bank item delivery schema, scoring rubric, remediation path mapping to Partner's content catalog
• Enterprise surface: Workforce Intelligence Report template (one section), Hiring Calibration Workshop scope summary

Commercial package

• Workforce Readiness Content License Agreement summary
• Platform Integration Order Form draft (for Partner's internal review)
• Commercial terms summary (pricing, billing model, branding tier options)
• Next-phase options: Platform Integration scope recommendation and strategic license overview

Out of scope for this Pilot

• Full role taxonomy (all 12+ archetypes) — included in Platform Integration
• Full Q&A bank beyond the 100-item pilot export — included in Platform Integration or content-license expansion
• Live Job Navigator API — included in Platform Integration
• Hiring Calibration Workshop facilitation — included in Platform Integration
• Workforce Intelligence Report authoring — included in Platform Integration
• Platform engineering labor, LMS implementation, or HTB-native ingestion adapter
• White-label branding of Pilot content (Pilot content carries aisecurity.llc attribution)
• Customer PII processing or DPA (Pilot uses anonymized or synthetic data only)

3. Deliverables Checklist

4. Partner Responsibilities

Partner must provide during the Pilot:

• Platform architecture brief: description of practitioner profile infrastructure, assessment/cert infrastructure, and enterprise admin portal
• Content catalog input: export or summary of existing AI security learning paths, lab tracks, and cert tracks (for content mapping in Deliverable 3–5)
• Domain, role, and lab-catalog mapping preferences for the first HTB-native ingestion adapter (within 2 business days of SOW signature)
• Technical owner: one named engineering contact who will review integration specs and confirm they are actionable
• Commercial owner: one named BD or product contact who will review the commercial package

5. Timeline

Timeline assumes Partner provides architecture brief and domain/role selections by Day 2. Delays in Partner inputs may extend the timeline.

6. Fees

7. Data Handling

• No Partner customer PII or practitioner data is transferred to aisecurity.llc during the Pilot
• If Partner provides a content catalog export, it must contain no practitioner or customer PII
• Pilot content delivered by aisecurity.llc remains aisecurity.llc IP; Partner may use it for internal evaluation only during the Pilot period
• Pilot content must be destroyed or returned if Partner does not proceed to Platform Integration within 90 days of Pilot completion

8. Acceptance Criteria

The Pilot is accepted when Partner confirms in writing:

1. Role taxonomy content is actionable for integration into the practitioner surface
2. Q&A bank items are suitable for the certification surface (format, domain, difficulty)
3. Integration architecture specs are sufficient for Partner's engineering team to scope an integration build
4. Commercial package is ready for Partner's internal commercial review

If Partner identifies a material deficiency in any deliverable, Partner must notify aisecurity.llc within 5 business days of delivery. aisecurity.llc will address material deficiencies within 5 business days of notice.

9. Next-Phase Options

At Pilot conclusion, Partner may:

1. Proceed to Platform Integration — execute the Platform Integration Order Form (4–8 weeks, $180k–$350k+) to activate all three surfaces under white-label branding
2. Proceed to Annual Content License only — execute a content license for the Pilot content volume without full Platform Integration implementation support
3. Proceed to Strategic License negotiation — contact commercial@aisecurity.llc to discuss IP option, exclusivity, and co-development
4. No further engagement — Pilot concludes; Partner destroys Pilot materials per Section 7

aisecurity.llc will deliver a written next-phase proposal at Day 14 of the Pilot.

This SOW description is for planning and discussion. The executed SOW governs. All commercial terms are final when the SOW is signed. This document does not constitute legal advice.