How ravora0809/signalpost works
Signalpost researches Norwegian companies and collects public evidence about them. The main workflow validates an organization number, checks PostgreSQL first, and fetches from Brønnøysundregistrene only when the company is absent; verified company data is then persisted and returned. A separate source-collection workflow discovers candidate URLs, fetches and verifies their content, and stores source metadata and hashes. Source relationships follow the README and SOURCE INDEX; excerpts do not expose every route or service call, so uncertain connections are omitted.
Main entry points: routes.py HTTP routes · source.py Source collection · discovery.py Candidate discovery · config.py Runtime settings
Components 17
Company research
- HTTP routes
app/api/routes.py - Company validation
app/schemas/company.py - Company lookup
app/services/company.py - Brreg client
app/sources/brreg.py
Source collection
- Source collection
app/services/source.py - Candidate discovery
app/sources/discovery.py - Search provider
app/sources/search.py - Web fetching
app/sources/web.py - Identity verification
app/validation/source_identity.py - Source schemas
app/schemas/source.py
Data layer
- Database sessions
app/database/database.py - Company and source records
app/database/models.py
Runtime configuration
- Runtime settings
app/config.py
Other components
- API caller
- Brreg registry
- Configured search
- Public websites
Connections 22
- API caller → HTTP routes: sends requests
README.md - HTTP routes → Company validation: validates input
app/api/routes.py - HTTP routes → Company lookup: requests research
app/api/routes.py - Company lookup → Company and source records: reads and persists
app/services/company.py - Company lookup → Brreg client: fetches missing company
app/services/company.py - Brreg client → Brreg registry: requests registry data
app/sources/brreg.py - HTTP routes → Database sessions: injects session
app/api/routes.py - Database sessions → Runtime settings: loads database URL
app/database/database.py - HTTP routes → Source collection: collects sources
app/api/routes.py - HTTP routes → Company and source records: queries source records
app/api/routes.py - Source collection → Candidate discovery: discovers candidates
app/services/source.py - Candidate discovery → Brreg client: adds registry candidate
app/sources/discovery.py - Candidate discovery → Search provider: searches candidates
app/sources/discovery.py - Search provider → Configured search: queries optionally
app/sources/search.py - Candidate discovery → Web fetching: fetches candidates
app/sources/discovery.py - Web fetching → Public websites: retrieves pages
app/sources/web.py - Source collection → Web fetching: fetches candidate URLs
app/services/source.py - Source collection → Identity verification: verifies identity
app/services/source.py - Source collection → Company and source records: stores source evidence
app/services/source.py - Source collection → Runtime settings: uses collection limits
app/services/source.py - Candidate discovery → Runtime settings: configures discovery
app/sources/discovery.py - Search provider → Runtime settings: loads provider config
app/sources/search.py