JTF-Certified Partner Firm
Status: active. Jurisdiction: lagos.
2027-03-01Trust wall
Trust claims must come from live platform state. Expired or revoked certifications are excluded from the current list.
Status: active. Jurisdiction: lagos.
2027-03-01Status: active. Jurisdiction: british-columbia.
2027-04-01Operators, firms, clients, and admins act through scoped accounts and credential disclosures.
Assignments, shifts, check-ins, incidents, notes, evidence, reports, and billing are append-only workflow rows.
AI drafts remain scoped to approved source hashes and require approval for high-impact reuse.
External email, SMS, payments, comms, storage, and ads run behind readiness checks and provider-call hashes.
Maps each requested service to credentials, jurisdictions, partner coverage, and command controls before signature.
Shows tenant, permission, provider-readiness, retention, and audit controls in procurement-safe language.
Exports approved mission timeline, staffing decisions, incident evidence, reports, invoices, and closeout notes.
Lists AI briefs, source hashes, reviewer approvals, and reuse limits for regulated or client-facing artifacts.
Vendor eligibility and renewal evidence feed the procurement hub.
Global institutional registration status stays visible to buyers.
Canadian procurement readiness is part of the trust wall.
Alliance-facing readiness remains a launch-track item.
Requests capture authorized requester, procurement contact, security lead, consent, and lawful basis before operational handoff.
Quote, statement of work, acceptance, approval, and mission requirement hashes stay linked for client and audit review.
Each service request declares standard, restricted, or client-approved-only evidence handling before incidents can be released.
Client-safe reports, invoices, history exports, and after-action artifacts are generated from approved mission records.