News, videos and posts supply signals. Evidenced discovery uses bounded search-provider requests; continuous direct YouTube/Instagram/X crawlers are not proven.
Instance
External · permitted search
Trigger / time
Within the approved daily run
Write destination / artifacts
Search terms → URL, title, summary; no raw videos or cookies.
https://api.search.brave.com/res/v1/web/search
https://api.tavily.com/search
https://www.googleapis.com/customsearch/v1
Validation status
Source code and recorded daily run checked
Novelty
Established technology / method
Source evidence
Versioned source code + daily report
Editorial architecture classification, not a calculated innovation score. Technical novelty requires a dated comparison with known solutions.
Codex carries out assigned implementation, verification and deployment. Claude belongs to the cooperative agent lane; an installed CLI does not prove an authenticated model job.
Instance
Local Codex; Claude lane by assignment and authentication
Trigger / time
By assignment · isolated workspace
Write destination / artifacts
Change → tests → independent acceptance → approval gate; no unrestricted production writes.
Codex
Claude
Validation status
Role documented; actual execution depends on assignment
Novelty
Setup integration · novelty open
Source evidence
Documented agent lanes; no individual model job attested
Editorial architecture classification, not a calculated innovation score. Technical novelty requires a dated comparison with known solutions.
Goals, purpose, budget and relevant approvals remain yours. Agents consolidate the decision into a concrete proposal; approved routine does not require repeated consent.
Instance
Human accountability · DMS
Trigger / time
When a specific gate needs a decision
Write destination / artifacts
Decision / rule → BOE assignment and traceable approval state.
HITL
Validation status
Responsibility defined; an actual decision needs separate evidence
Novelty
Established technology / method
Source evidence
User-defined approval and responsibility rules
Editorial architecture classification, not a calculated innovation score. Technical novelty requires a dated comparison with known solutions.
Each element needs three separate answers: what was checked, what is new, and which source supports the claim? An established tool can be part of a new combination. Novelty establishes neither truth nor value.
Validation path for an individual news signal
1 · Identify
Preserve claim, original URL, publisher, publication date and discovery time. Trace copies and syndicated reports to one origin.
2 · Validate
Read the primary source and attribute supporting and contradicting evidence. Distinguish plans, prototypes, available products and measured use. Without a primary source the claim remains unchecked.
3 · Assess novelty
Compare with dated prior knowledge: known, new to the local collection, a new combination or a new evidenced business capability. Without comparison, novelty remains open.
4 · Decide
Display source strength, novelty, relevance and maturity separately. BOE checks the need and permitted use; measured evidence is required to assess value.
0
Known
The same claim already appears in dated prior knowledge.
1
New locally
New to local memory; no global novelty claimed.
2
New combination
Known components form a new, specifically described application.
3
New evidenced business capability
A dated comparison and primary evidence show a previously unproven business capability.
?
Open
Primary source or comparison is missing. No value is guessed.
Evidence per signal: claim · source URL · publisher · publication/discovery time · supports/contradicts · independent origin · comparison baseline · novelty with rationale · relevance · reviewer · review time · open questions.
Proposed assessment framework, not a new production scoring function: existing radar rules and stored candidates remain unchanged. No news score is assigned without a fresh individual review. Three search providers do not mean three independent sources.
X → B · A · P · P · O
From Business Architecture to BAPPO
Start with X: a market need, a problem and verifiable value. Business Architecture defines the required business capability; BAPPO connects its implementation.
Business
X → offering → value
CAT supplies market signals. BOE turns them into concrete problems, offerings and required business capabilities. A business capability profile describes the need; a proven delivery unit requires implementation and value evidence.
Architecture
Application + Data + API
Applications: Ruby radar, Python context services, Hindsight, GitHub and the public website. Data: MySQL for candidates, SQLite for sources, PostgreSQL for Hindsight. APIs define bounded discovery, permitted intake and source-grounded recall.
Process
Discover → Remember → Verify → Learn
The daily run collects and classifies signals with fixed rules. The separate memory lane checks source and hash, processes permitted documents and validates recall. Codex and Claude handle bounded assignments; publication follows review and checks.
People
You · HITL · clear decisions
People set goals, budgets, purpose and approvals. Agents prepare a concrete, reviewable result. Approved routine work continues; new external effects, missing permissions or risks require a decision.
Organization
Digital Market Services orchestrates
DMS owns structure, roles, rules and processes. CAP Runtime operates instances, CAP BRAIN governs sources and memory, implementation and review lanes validate changes. Providers supply partial business capabilities; using them does not grant automatic shared approval.
◎
Less effort for you: decide at the right point.
A brief decision card states the goal, concrete result, value, cost and unresolved risks. Approved routine work does not need another click. New permissions, sensitive data, legal or financial commitments and releases follow their respective gates.
What runs, when and where?
Instance
Trigger / time
Programs
Write destination / artifacts
CAT · radar
Mac mini · macOS · local automation Daily 08:30 · Europe/Berlin; scoped assignments also possible
/ai-signal-radar/ · /ai-signal-radar/architecture.htmlStatic HTML / CSS / JS
DMS and the provider chain
DMS owns structure, roles, rules and processes. CAP Runtime operates instances, CAP BRAIN governs sources and memory, implementation and review lanes validate changes. Providers supply partial business capabilities; using them does not grant automatic shared approval.
This map explains the evidenced setup and its limits. It does not query internal services or display live telemetry. 24/7 is a product goal, not proven availability.