Formal publications
ALCUB3-authored reports with abstract, methods, limitations, citations, and approval state.
Publication Registry
Technical reports, methods notes, and evidence briefs.
Reports collects formal ALCUB3 publications, scoring methods, validation notes, and public-facing summaries that support product and mission claims.
Research pipeline
What exists, what is moving, and what still needs evidence.
| Report | Type | Status | Primary bridge |
|---|---|---|---|
| The Water Risk Information Gap Toward property-level water intelligence from public data. | Technical report | Drafting; policy review required before publication | Impact / Water Intelligence |
| Evidence standards for memory-backed agent claims Minimum evidence bar for execution, memory, trust, and observability claims. | Methods note | Published | Methods |
| Why the Control Plane Is Becoming the Real Product in Agentic Systems Synthesis from ManyIH, PAC-Bench, c-CRAB, and sovereign-AI demand signals. | Research brief | Evidence Gathering | Higher-trust planning |
| Fault Tolerance in Autonomous Agent Organizations Why verification alone is insufficient when agent organizations behave like distributed systems. | Working paper | Outline | Labs |
| Three Architectures for Agent Grounding in Defense Contexts Comparison of ontology, hardware, and domain-aligned training approaches. | Strategy paper | Evidence Gathering | Platform track |
| Satellite-backed water intelligence and source limits How public records, satellite observation, and segmentation can support water-risk claims. | Evidence brief | Dataset / Method Pending | Impact |
Publication types
Different claims need different publishing weight.
How scores are made
Scoring methods, source rules, validation standards, caveats, and applicability limits.
Shorter public summaries
Reader-friendly summaries tied to product claims, demos, and field-facing surfaces.
Promotion flow
Research moves through visible stages.
Claim and scope
The owner captures sources, gaps, caveats, and which public surface the work supports.
Policy gate
Publication review, legal/IP check, and Chairman approval are required before release.
Versioned record
The work becomes a technical report, methods note, evidence brief, benchmark entry, source note, or learning module.
Cross-links
Reports route readers to proof and action.
Platform
Platform-facing reports validate agent runtime, memory, trust boundaries, and secure deployment.
Open platform track →Impact
Mission-facing reports validate water intelligence, public-interest methods, and partner-ready proof.
Open impact track →Sources
Every report depends on clear sourcing. The sources page explains the provenance chain.
Open sources →