Development as evidence of how we work.

Selected work demonstrates IRELCO’s knowledge and in-house implementation capability. Each example states its maturity and boundaries.

A development example is evidence of relevant capability—not a claim of accreditation, enterprise scale or universal production readiness.

01 · Product-safety evidence ecosystem

FOLO-UP

Active development · Public Whistle extension

The problem

A person may notice a potentially unsafe or recalled product online, but that observation must be captured, structured and reviewed before anyone can responsibly act on it.

What has been developed

Whistle, a public Chrome extension for submitting an unverified listing signal
Marketplace acquisition from browser network traffic, full HTML, structured product data and reviews
SHA-256-linked capture files, sources, timestamps and chain-of-custody records
Find–Verify–Resolve case workflows, routing, access history, correspondence and exports
Image extraction, reverse-image research and controlled human confirmation
AI-assisted classification and multilingual review with mandatory human control

What it demonstrates

Browser-extension development, API-independent acquisition, data engineering, evidence integrity, case management, analyst tooling, reporting and responsible AI design.

Boundary

A Whistle submission is an unverified listing signal for evidence capture and controlled human review. It is never presented as a confirmed safety finding. FOLO-UP supports evidence-led work; it does not provide legal advice or regulatory determinations.

02 · Reusable technical foundation

Role-aware service platforms

Implemented components

The problem

Business applications often need the same dependable foundations before their specialist workflow can begin.

What has been implemented

Users, organisations, roles and invitations
Products, features, plans and entitlements
Subscriptions, seats and controlled access
Operational records, documents and audit histories
Administrative workflows and email outbox structures

What it demonstrates

IRELCO can design and implement the core architecture of scoped multi-user services, then connect it to a domain-specific workflow.

Boundary

The existence of components does not imply that every configuration has completed independent security, resilience or regulatory accreditation. Those requirements must be specified and tested for the intended service.

03 · Operating model

Find–Verify–Resolve

Reusable workflow pattern

The problem

Research and investigation lose value when discovery, verification, ownership and resolution exist in disconnected tools.

The workflow

Find: capture a signal with its source and identifying context
Verify: acquire supporting material, compare identifiers and assign human review
Resolve: record decisions, correspondence, actions, status and outcome

What it demonstrates

Case architecture, task routing, access histories, evidence links, correspondence generation and structured SQL/JSON/CSV export.

Where it can transfer

The pattern is relevant wherever a high-volume observation must become an inspectable case and a governed action—not only in product safety.

Evidence discipline

What we deliberately do not overstate.

Responsible case studies distinguish current implementation from historical documentation, concepts and claims that still require validation.

Hold

Performance claims

Internal performance estimates remain omitted from the public offer until their basis, conditions and reproducibility have been validated.

Confirm

Historical system descriptions

Older FOLO-UP documentation describes rich recall, listing, case, stakeholder, task and trend structures. Only features confirmed in current implementation are described as current.

Exclude

Concept-stage platforms

Concepts that have not started development are not presented as delivered experience or customer-ready services.

Relevant experience

Which part of this work connects to your challenge?

We can discuss a specific data, evidence, workflow or product-development requirement without forcing it into an existing product.

Start a conversation