Technical landing

Inspect the system behind RoyFlow's creator workflow.

This page is built for engineering and licensing evaluation. It maps ingest, normalization, matching, pitch flow, outcomes, and verification into one reproducible chain.

System chain

Ingest -> Normalize -> Match -> Pitch -> Outcome -> Verify

Ingest

source_id + ingest_run_id + raw_snapshot_ref

Bright Data integration

Normalize

taxonomy_version + confidence thresholds

canonical requirement model

Match

scoring_version + reason_codes + hard_violations

Neo4j explainability

Pitch

packet_ref + signed links

trace-linked outreach state

Outcome

event-based progression

callback/placement verification

Verify

evidence replay endpoints

append-only EventLog continuity

Explainability

Match decisions are traceable and reviewable.

Worked example

score_total: 0.87

scoring_version: v1.1.0

taxonomy_version: 1.0.0

reason_codes: [GENRE_MATCH, MOOD_MATCH, TEMPO_RANGE_MATCH]

hard_violations: []

disqualifier examples: FORBIDS_THEME_HIT, MISSING_REQUIRED_DELIVERABLE

Evidence endpoints

  • GET /v1/evidence/trace?brief_id=...
  • GET /v1/matches/{match_id}
  • GET /v1/ingest/runs/{run_id}
  • GET /v1/events?entity_id=...

Reliability targets

Published targets for operational planning.

Values below are target commitments, not claimed measured outcomes.

Target

API availability >= 99.5%

Target

Evidence endpoint availability >= 99.7%

Target

Public app uptime (app.royflow.ai) >= 99.7%

Target

Ingestion freshness median <= 24h

Target

Parse success >= 95%

Target

Ingest run completion >= 98%

Target

Match compute p95 <= 1500ms

Target

Event emission reliability >= 99.9%

View all reliability and data-quality targets

Quarantine rate <= 15%

Explainability completeness = 100%

Hard-filter false-allow rate = 0%

Dedup false-merge rate < 1%

EventLog immutability violations = 0

Provenance completeness = 100%

Operations and governance

Built on managed systems with explicit controls.

Platform posture

  • Bright Data integration for brief ingestion
  • Managed Neo4j for graph matching and explainability
  • Algolia SaaS for search and audit retrieval
  • Observability dashboards and documented runbooks

Security and data posture

  • JWT + RBAC access control
  • Append-only EventLog timeline integrity
  • Encryption at rest and TLS in transit
  • Public-source-only ingestion with source governance controls

Technical CTA

Review the architecture, then run the workflow live.