Receive
Use an authorized non-public channel. Do not place controlled, classified, export-restricted, customer-sensitive, credential, or secret material into the public website repository.
CONTRACTING
Procurement facts without invented credentials.
Program offices and prime contractors need a legal-entity, cyber, security, export, supply-chain, and business-systems picture before they rely on a supplier. This page answers those questions using only evidence present in the current repository and marks everything else explicitly.
PUBLIC PROCUREMENT PROFILE
What can a government buyer verify from this site today?
WeaponizedAutonomy.com can verify its public software scope, public data boundary, first-party web architecture, release controls, and machine-intelligence operating model. It does not publish a SAM registration, UEI, CAGE code, CMMC status, Facility Clearance, export credential, contract vehicle, customer list, or past-performance claim unless documentary evidence exists in the repository.
DUE DILIGENCE MATRIX
The questions a contracting officer or prime should ask.
WeaponizedAutonomy.com publishes a procurement or assurance claim only when the current repository contains evidence sufficient to support that claim. Absence from this profile means not publicly asserted, not necessarily absent in the underlying business.
| Due-diligence question | Public status | Current answer |
|---|---|---|
| What legal entity will sign the contract? | Not publicly asserted | WeaponizedAutonomy.com is the verified site and brand identity in this repository. The contracting legal entity name is not documented here and must be confirmed through an authorized business channel before reliance. |
| Is the contracting entity actively registered in SAM.gov? | Not publicly asserted | No active SAM.gov registration record or documentary proof is present in this repository. The site does not claim active federal prime-award registration. |
| What are the UEI and CAGE codes? | Not publicly asserted | No verified Unique Entity Identifier or CAGE code is stored in the inspected repository, so neither identifier is published or implied. |
| Which NAICS, PSC, size, and socioeconomic classifications apply? | Not publicly asserted | No verified NAICS, PSC, small-business size determination, or socioeconomic certification is present in the repository. These must be matched to the actual legal entity and opportunity. |
| Which contract vehicles, schedules, IDIQs, OTAs, or prime agreements can be used? | Not publicly asserted | The public site does not claim a contract vehicle, schedule, IDIQ position, OTA consortium membership, or existing prime agreement without documentary evidence. |
| Can WeaponizedAutonomy.com support a prime or subcontract role? | Contract dependent | The site is designed for government program offices and authorized defense-industry teams, but eligibility, flow-downs, privity, and the contracting path must be established for the specific opportunity. |
| What ownership, control, and FOCI facts apply? | Not publicly asserted | The repository does not contain verified corporate ownership, highest-level owner, foreign-interest, or FOCI determination records. No public representation is made. |
| Does the company hold a Facility Clearance or cleared personnel? | Not publicly asserted | No Facility Clearance, personnel-clearance, sponsoring relationship, or classified-contract evidence is present in the repository. Classified access must never be inferred from the site's defense focus. |
| Is the entity JCP/DD Form 2345 certified or otherwise authorized for controlled technical data? | Not publicly asserted | No JCP, DD Form 2345, export authorization, or equivalent controlled-technical-data credential is present in the repository. Do not transmit controlled technical data through this public site. |
| What ITAR/DDTC registration or export-control status applies? | Contract dependent | The public repository does not establish an ITAR/DDTC registration or export-license status. Applicability depends on the actual legal entity, defense article/service, technical data, parties, and transaction. |
| What CMMC, NIST SP 800-171, or SPRS status can be verified? | Not publicly asserted | No CMMC assessment/certification, NIST SP 800-171 DoD assessment score, SPRS record, SSP, or POA&M evidence is present in this repository. The public website is not presented as a CUI processing environment. |
| Can the entity make current Section 889 or other SAM representations and certifications? | Not publicly asserted | No entity-wide representation is made from this repository. The public website's zero-required-third-party-runtime design is a software fact, not a substitute for a corporate reasonable inquiry or solicitation representation. |
| Are DCAA/DCMA accounting, estimating, purchasing, property, EVMS, or related business systems approved? | Contract dependent | No approval or adequacy determination for any government contractor business system is present in the repository. Requirements vary by contract type and clause set. |
| What insurance, bonding, or indemnification coverage is in force? | Not publicly asserted | No current certificate of insurance, bond, or coverage schedule is present in the repository. Coverage must be verified for the contracting entity and contemplated scope. |
| What government or prime-contractor past performance can be verified? | Not publicly asserted | The public repository contains no verified customer list, award history, CPARS record, subcontract reference, or permission to publish program names. No past-performance claim is made. |
No badge without evidence. “Not publicly asserted” means the current source package does not prove the credential; it does not assert that the underlying business lacks it.
Evidence available upon request where applicable. Supporting procurement, security, corporate, insurance, and past-performance materials may be made available to authorized government or prime-contractor reviewers upon request where those materials exist, are applicable to the contemplated engagement, and disclosure is permitted. A request does not imply that any particular registration, certification, clearance, contract vehicle, customer reference, or other credential exists.
Materials may be withheld, redacted, or provided only through approved channels when required by law, regulation, classification, export control, contract, customer direction, confidentiality, privacy, security, or need-to-know restrictions. No disclosure will be made where prohibited.
EVIDENCE PROMOTION
How a credential moves from private evidence to a public claim.
Supporting material is reviewed through a source-only evidence workflow. Nothing is auto-published. A verified record remains private metadata until an authorized reviewer separately approves public disclosure and the canonical procurement profile is changed in a versioned release.
Verify
Confirm the contracting legal entity, source authority, evidence date, expiration, applicable scope, and whether disclosure is legally and contractually permitted.
Record
Preserve only safe metadata and, when useful, a source digest. The underlying document stays in approved external custody rather than becoming a public deploy artifact.
Publish
Only explicitly approved public facts are promoted through a manual procurement-profile edit, publication regeneration, automated checks, and a new release.
QUALIFICATION PACKET
What a program office or prime should request before reliance.
The exact packet depends on the opportunity. A defensible qualification review normally separates entity identity, contract eligibility, cyber/CUI posture, classified/export eligibility, supply-chain representations, business systems, and technical assurance rather than treating a marketing page as proof.
Entity & Award Eligibility
Contracting legal name, address, active SAM registration when applicable, UEI, CAGE, ownership/control, current representations and certifications, NAICS/PSC alignment, size and socioeconomic status.
Cyber & CUI
Applicable CMMC status, NIST SP 800-171 boundary, current DoD assessment/SPRS evidence when required, SSP/POA&M handling, incident-reporting obligations, cloud constraints, and subcontract flow-downs.
Classified & Export
Facility/personnel clearance facts, sponsorship and DD Form 254 requirements, ownership/FOCI review where applicable, JCP/DD Form 2345 status, export registrations, licenses, agreements, and data-custodian controls.
Supply Chain
Section 889 and other required representations, software/component inventory, SBOM and provenance practices, third-party dependency disclosure, update integrity, source control, and customer data-rights boundaries.
Business Systems
Contract vehicles, teaming path, rates and invoicing model, insurance, accounting and estimating controls, purchasing/property requirements, EVMS applicability, and any government adequacy or approval evidence actually required.
Technical Evidence
Architecture, interfaces, configuration baseline, verification plan, test results, secure-development evidence, change control, deployment boundary, failure handling, transition plan, and acceptance criteria.
FIRST CONTACT
Send enough context to qualify the opportunity—nothing controlled.
Useful first-contact information includes the unclassified opportunity or program identifier, desired prime/subcontract role, software or systems-engineering problem, anticipated schedule, place of performance, known compliance requirements, expected data classification/CUI boundary, desired contract path, and the party responsible for controlled follow-on exchange.
Do not send CUI, classified information, export-controlled technical data, operational mission data, target data, system vulnerabilities, access credentials, source that is not cleared for public release, or weapon-employment parameters through the public website or ordinary first-contact email.
ASSURANCE
Need the software-trust side of due diligence?
The assurance profile separates repository-verified controls from enterprise certifications and program-specific evidence.
Review assurance profile