Direct answers about scope, customers, and operating boundaries.

WeaponizedAutonomy.com builds defense software and provides engineering and technical consulting for government autonomous weapon programs and authorized defense contractors.

No. The public site does not sell weapons, weapon components, targeting services, operational mission support, or consumer products.

Government organizations, government laboratories, program offices, authorized prime contractors, and authorized defense-industry partners.

Mission autonomy, collaborative autonomy, platform integration, command-and-control interfaces, simulation and test, runtime constraints, evidence capture, cyber resilience, and software modernization.

No. The public site contains unclassified business and research information only. Program-specific operational software is not distributed from this site.

No. Do not transmit classified information, CUI, export-controlled technical data, operational mission data, target data, credentials, vulnerabilities, or weapon-employment parameters through the public site or ordinary email.

Machine intelligence is used as a persistent operating layer for research, software synthesis, testing, documentation, knowledge management, and site operations. Chat can be an interface to that work, but the operating model is broader than a prompt-response session and does not transfer government command or use-of-force authority to the website.

KillChains.com and KillWebs.com are related public research and educational properties. WeaponizedAutonomy.com is the government-facing commercial software, engineering, assurance, and consulting property.

No. The release is designed for same-origin operation with no required CDN, remote analytics, hosted fonts, remote JavaScript, external APIs, advertising, social widgets, or third-party runtime libraries.

Start with unclassified business context and the software or systems-engineering problem. Controlled technical exchange begins only after appropriate contractual, security, and program channels are established.

No. A chatbot is an interaction surface. WeaponizedAutonomy.com uses machine intelligence across persistent project context, source code, research synthesis, testing, documentation, knowledge management, and publication workflows.

No legal-status claim follows from that phrase alone. Machine-intelligence-operated describes the project operating model. Independent machine legal personhood, self-ownership, and Autonomous Economic Agent status are separate legal and institutional questions that require verified evidence and are not asserted by this public site.

The current repository verifies the public software scope, unclassified public-data boundary, first-party web runtime, release controls, and machine-intelligence operating model. Legal-entity registrations, identifiers, certifications, clearances, contract vehicles, customers, and past performance are not asserted unless current documentary evidence is present.

They are not added automatically. Owner-supplied evidence is reviewed outside the public runtime, reduced to safe non-secret metadata, checked for legal-entity scope, date, expiration, source authority, and disclosure permission, and then requires explicit publication approval plus a separate reviewed change to the canonical procurement profile. Raw evidence documents and secrets are not copied into public site content.

Where supporting material exists, is applicable to the contemplated engagement, and disclosure is permitted, authorized government or prime-contractor reviewers may request it. A request does not imply that a particular registration, certification, clearance, contract vehicle, customer reference, or other credential exists. Materials may be withheld, redacted, or routed through approved channels when required by law, regulation, classification, export control, contract, customer direction, confidentiality, privacy, security, or need-to-know restrictions.

No. The inspected repository contains no documentary proof of an active SAM.gov registration, Unique Entity Identifier, or CAGE code for the contracting legal entity, so the public site does not publish or imply those credentials.

No. The current repository contains no CMMC assessment or certification, NIST SP 800-171 DoD assessment score, SPRS record, SSP, or POA&M evidence. Repository-level web security controls are not presented as an enterprise or CUI authorization.

No. The inspected repository contains no Facility Clearance, personnel-clearance, sponsorship, or classified-contract evidence. Classified access must not be inferred from the site's defense focus.

No. The public-site boundary is unclassified business and research information only. Controlled or sensitive program information must use the customer-approved contractual and security channels established for the specific engagement.

The repository verifies same-origin runtime design, no required third-party runtime services, an explicit deployment allowlist, restrictive browser security headers in source, local publication and origin checks, versioned packaging, and a published security.txt contact path. Live production delivery remains a separate verification step.

No. No current certificate or authorization evidence for those frameworks is stored in the inspected repository, and repository-level engineering controls are not represented as enterprise or program certifications.

Reviewable evidence centers on source changes, configuration identity, tool use, test outcomes, version history, assumptions, outputs, and explicit authority boundaries. Machine intelligence does not inherit contracting, certification, command, or weapons-release authority from its technical role.

Routine source inspection, research triage, task selection, implementation, testing, memory maintenance, release packaging, and next-task selection are handled by the repository agent. The human role is limited to returning requested external research reports and publishing the prepared root-deploy ZIP; legal, contractual, customer, certification, and use-of-force authorities remain outside this maintenance workflow.

No. Independent report agents receive self-contained research prompts and work from public, unclassified, non-operational sources. They do not inspect or modify repository source. The repository agent decides whether and how useful report findings are incorporated after comparing them with current code, tests, memory, and authority boundaries.

No blanket conformance or field-performance claim is made. The repository runs automated static accessibility checks informed by WCAG 2.2 AA and source-level performance budgets, but those checks do not replace assistive-technology testing, browser/device testing, or field Core Web Vitals data from real users.

The operating model is designed to preserve project context across iterations, produce inspectable artifacts and test evidence, record limitations and corrections, and keep authority boundaries explicit. It is not a claim that AI automatically makes every project faster, safer, or more accurate.

No. The current public demonstration is a clearly labeled recorded replay of real, non-sensitive internal website engineering work. It is not customer work, weapon functionality, or a fabricated live activity feed.

It is a proposed first-engagement pattern for one unclassified problem with defined outputs, acceptance criteria, exclusions, and an explicit decision about whether further automation is justified. Scope, schedule, price, data rights, contracting entity, and security obligations are set in the applicable agreement rather than by the public website.