Shared intelligence
Perception, ontology, evidence methods and operational context across the ecosystem.
ARGOS
Intelligence, surveillance, defence and autonomous operations, brought together in a customer programme.
THE ARGOS DEPARTMENT AND COMMERCIAL OFFER
ARGOS is Wyrd’s shared intelligence department and commercial division for intelligence, investigation and governed operational programmes. Its development portfolio includes data analytics, investigative software, controlled information collection, surveillance with defined privacy protections, defence intelligence, and programmes involving drones, unmanned vehicles and autonomous-system control. Each programme is scoped through explicit authority, access boundaries, oversight requirements and reviewable evidence.
Across Wyrd, ARGOS develops shared perception, ontology, evidence methods and operational context. For customers, it brings selected capabilities together into a defined programme, with its own delivery, integration and support responsibilities.
THE TECHNOLOGY, SIMPLY
Illustrative design. Each configuration defines its scope and controls.
Perception, ontology, evidence methods and operational context across the ecosystem.
Selected intelligence, surveillance, defence, digital and physical capabilities, with defined delivery and support.
Knowledge, perception and executive intelligence.
DIGITAL CAPABILITIESBounded digital work across connected systems.
PHYSICAL-SYSTEMS DIVISIONSeparately qualified machines, vehicles and fleets.
ARGOS can bring the selected capabilities together in one customer programme. WUI remains the shared commercial platform; Corpus retains physical-system qualification responsibilities.
Connect sources, entities, events and dependencies. Develop research, alerts, scenarios and continuously refreshed strategic assessments.
Bring authorised observation feeds, sensing and monitoring into a connected operating picture, including interfaces such as Eyes of God.
Develop tools for acquiring and examining digital evidence, monitoring specified activity on designated devices, collecting information for investigations and remotely administering authorised systems. Depending on the programme, this can include examining files, system logs and device records; observing defined endpoint activity; gathering information from approved sources; and performing permitted administrative actions.
Each programme defines the devices, accounts, sources and information within scope, the actions available to operators and when their authority expires. Its design includes access restrictions, records of collection and administrative actions, evidence-handling procedures, retention periods and deletion requirements. Where personal identity is involved, observation and identity revelation receive separate controls and approval requirements.
Support strategic and operational assessment, situational awareness and decision support under the institution’s authority.
Combine suitable platforms, sensing, software, governed autonomy and fleet coordination in a customer programme.
Integrate, direct, coordinate, monitor and control eligible systems within defined authority, mission and operating limits.
Footage illustrates the fields these programmes address. It does not depict a deployed Wyrd surveillance system, defence installation or autonomous fleet.
Reference footage from military exercises, supplied through DVIDS. The appearance of U.S. Department of War (DoW) visual information does not imply or constitute DoW endorsement. These are illustrative environments, not Wyrd equipment or deployments.
SURVEILLANCE WITH PRIVACY PROTECTIONS
Observation creates power over the people and places being observed. Our approach places privacy controls, limits on authority and inspectable records within the programme’s design. The operator’s ability to understand a situation must be considered alongside the rights and safety of the people who appear within it.
For person-identification programmes, ARGOS’s design separates a pseudonymous observation from access to a person’s identity. Moving from where an authorised subject was observed to who that subject is requires its own controlled process. The relevant authority, purpose, time limit, independent approval and identity custody must be defined for the deployment.
A pseudonym can still reveal patterns in a person’s life. The observations themselves therefore need purpose limits, access controls and retention rules, alongside the additional protection around identity. The usefulness of an operating picture does not remove responsibility for what can be inferred from it.
The person-tracking design represents people through pseudonyms in the operating view. Identity is kept separately, with access controlled beyond ordinary console use.
An identity-reveal request is checked against a registered, scoped, unexpired, subject-specific authorisation. The warrant-based implementation records purpose and justification with the request.
The design requires an approver distinct from both the requester and the warrant issuer. One operator should not be able to create the authority and approve its own use.
Identity recovery uses split custody outside the console. The configured custody quorum and the warrant-signing authority need operational separation from the ordinary operator.
The implementation provides retention expiry and targeted purge mechanisms for sealed identity material. The adopted schedule governs how long a programme keeps its records.
Sealing, warrants, reveals and purges are designed to leave signed, linked records. A pseudonymous inventory and oversight export let the responsible reviewers examine use of the system.
These are design controls with implementation evidence, not a claim of certified compliance or a deployed person-tracking service. The customer, qualified counsel and responsible data-protection functions must adopt the jurisdiction-specific deployment arrangements, including independent custody and signing.
PROTECTIONS THAT CAN BE EXAMINED
The safeguards need to create practical resistance to misuse: an expired request can be refused, an operator lacks unilateral identity access, a separate approver must consider the justification, and reviewers can examine the resulting record. Commissioning should test both permitted use and attempted misuse of the selected workflow.
Source governance matters as well. Person and object classification can fail, and a provider can mislabel a feed. The programme must examine those risks in its data agreements, validation and supervision. A classifier’s output alone cannot establish that a person’s information is outside the protected boundary.
The same responsibility continues after installation through training, access review, retention checks, incident handling and oversight. Shared technical controls support that work. The institution remains responsible for its purposes, its lawful authority and the consequences of how it operates the capability.
ANALYSIS AND THE OPERATOR’S VIEW
Continuously refreshed views of strengths, weaknesses, opportunities and threats, alongside social, technological, economic, environmental, political, legal and ethical developments. Keep source dates, confidence and changes visible.
Inspect operational entities, relationships, alerts, uncertainty, proposed responses and measured outcomes through a common view. A joined live installation remains a qualification target.
Explore Eyes of GodONE CUSTOMER PROGRAMME
A port operator connects permitted shipment records, equipment state and observations to the same assets and services. ARGOS identifies affected dependencies; WUI coordinates analysis; approved Agentix tasks can update connected digital systems. Qualified Corpus systems can support inspection or physical work where included.
Authority, the actual mission and physical safety are checked at their respective boundaries. The operator can follow the response and its observed outcome.
Illustrative programme. Integration and qualification required.DELIVERY AND CONTINUING SERVICE
Agree the problem, permitted sources, access rights and responsible operator.
Validate operational objects, relationships, source lineage and refresh.
Prove the selected intelligence or governed workflow, including refusal and recovery.
Maintain sources and models, train teams and provide the agreed support.
A customer can begin with read-only intelligence. Digital execution and physical systems are optional extensions with separate acceptance requirements.
CONFIGURED FOR THE CUSTOMER
Programmes can serve enterprises, financial institutions, utilities, industrial operators, cities, public authorities and defence institutions. Each defines its information rights, institutional authority, security boundary, service obligations and qualified systems.
Customer-controlled operation, local infrastructure, visible uncertainty, agreed source freshness and recovery are part of the delivery design. The four pillars and local-currency options are qualified for the selected configuration.
GET IN TOUCH
Stock footage illustrates operating environments. Each installed capability requires the acceptance appropriate to its scope.