Skip to content

Category: RegDelta · Regulatory Intelligence

When a rule changes, turn it into a reviewable change set — not a compliance promise.

RegDelta is Coreidea’s regulatory change-control platform. It anchors official versions, proposes obligation-level deltas, separates role-specific duties, records human applicability decisions, connects implementation evidence and preserves unresolved exceptions in a tamper-evident record.

Built for

  • Compliance officers
  • AIGC apps & platforms
  • Exporters & SMEs
Status
Live
Ledger step
Ledger step 4 of 4
Family
Regulatory
Access
Backend service, no front end
Listed
4 / 4

There is no public front end to open. Access is arranged on request: tell us your use case through the contact form.

Duty mapping
Role-aware
Source anchors
Versioned
Current standard
GB 45438
Review workflow
EN + ZH

What this page can show today

  • The register marks this track Live.
  • This track runs as a backend/internal service; there is no public front end to visit.
  • Capabilities below are the published feature list for this track.

Limits of this page

  • This track runs as a backend/internal service; there is no public front end to visit.
  • This page does not publish financials, headcount, or client names.

Key features

  1. 01

    Obligation-level regulation diff

    Regulation versions are compared clause by clause; every new, changed or removed obligation is matched to the products it touches.

  2. 02

    AIGC labeling compliance

    Drop-in SDK and API for China's AI-generated-content labeling mandate: explicit labels, embedded metadata manifests and transmission-duty verification.

  3. 03

    Milestone-verified escrow

    A delivery-verified escrow engine for prepaid and milestone-based industries. Funds release only against verified evidence.

  4. 04

    Tamper-evident evidence ledger

    Every decision is appended to a hash-chained ledger, so audits replay exactly what was known, when, and why.

Published links

Technology stack

TypeScript · Node.js · PostgreSQL · Ember Reason · Ember Guard

Related platforms

Family on the register: Regulatory Same family first, then tracks at the same lifecycle stage.

  • Same stage · Live

    CarbonBridge

    Carbon Compliance · CBAM

    Public product site

  • Same stage · Live

    LabForge

    Language Operations

    Backend service, no front end

  • Same stage · Live

    CoreAI

    Private AI Operations

    Invite only

  • Same stage · Live

    Ember AI

    Foundation Models

    Public product site

This cell on the investor register

Status and family write into the /investors URL. The holdings table lists every public track in that cell.

Open Live Regulatory holdings
4 / 4

JSON fields are copied from this row in src/data/platforms.ts. No financials.

How this track works

Audience on the left, the published Ember stack in the middle, capabilities on the right. Every node is copied from this track in the public register.

How this track moves work from its published audience through Coreidea and Ember into listed capabilities.

Inputs

Coreidea and Ember

Outputs

Select a node to inspect the published role and capability.

Compliance teams read PDFs. Obligations hide in diffs.

Regulatory text, effective dates, actor definitions, technical standards and enforcement signals change on different timelines. A document alert does not by itself identify the affected role, workflow or implementation evidence.

  • Change detection by luck

    Amendments bury obligation changes deep in revised text. Reading whole documents per release does not scale.

  • No product mapping

    Even when a change is spotted, the actor, trigger, product flow, exception and review owner still need an explicit applicability decision.

  • Evidence as afterthought

    Screenshots and email threads do not prove that the source set was complete, applicability was reviewed, the control was tested or exceptions stayed visible.

Obligation-level candidates, accountable decisions, inspectable evidence.

RegDelta keeps a controlled chain from official source to candidate delta, role and trigger, reviewed applicability, implementation artifact, observed test and unresolved exception.

  • Clause-by-clause diffing

    Official versions are compared into source-linked candidate duties — added, changed or removed — for accountable review.

  • Applicability matching

    The system proposes role, trigger and product-flow matches; a named reviewer owns the applicability rationale, scope and sign-off.

  • AIGC labeling workflow

    Reviewed deployments can connect explicit-label, implicit-metadata, export, declaration and dissemination-verification artifacts to the applicable role.

  • Milestone evidence state

    A reviewed milestone state can support a release or hold instruction to an integrated provider; RegDelta does not claim fund custody or licensed payment services.

From regulation feed to sealed evidence.

  1. Ingest versions

    Regulation texts enter as versioned, structured documents.

  2. Diff obligations

    The engine proposes source-linked candidate obligations and the nature of each change.

  3. Match products

    Role and trigger conditions are compared with the product registry for human applicability review.

  4. Generate actions

    Approved mappings produce scoped implementation tasks, artifacts, test requirements and review dates.

  5. Seal the ledger

    Source, decision, observed evidence and exceptions are appended to an integrity-verifiable record.

Three modules, one ledger.

  • Reg-diff engine

    Source-version comparison that emits candidate obligation deltas with exact source anchors for review.

  • AIGC label module

    Role-aware implementation support for explicit labels, implicit metadata, content identifiers, export paths, declarations and dissemination checks.

  • Escrow engine

    A milestone-evidence state machine that can emit release/hold instructions to an integrated provider, with dispute and exception states kept visible.

  • Evidence ledger

    Append-only, hash-chained records can reveal later alteration; they do not prove the original source, classification or judgment was correct.

Built for teams that answer to regulators.

  • AIGC apps & platforms

    Map generation, export, dissemination and user-declaration paths to reviewed label and metadata controls.

  • Compliance officers

    A change radar with product-mapped findings instead of a folder of PDFs.

  • Prepaid & milestone industries

    Keep milestone evidence, reviewer decisions and dispute states connected before an integrated provider receives a release or hold instruction.

  • Exporters & SMEs

    Maintain reviewed source/version and applicability records for selected rules without presenting automated matches as legal conclusions.

Questions, answered.

Is RegDelta legal advice?

No. RegDelta records source-linked candidate changes and supports a review workflow. Applicability, legal interpretation, implementation conformity and filing or enforcement outcomes require current counsel and accountable technical review.

What does the AIGC module cover?

Its stated scope covers role-aware explicit-label, implicit-metadata, export, declaration and dissemination-verification workflows. The Measures’ at-least-six-month log requirement applies to a specific no-explicit-label request path after agreement duties; it is not represented as a universal retention period.

How is the evidence ledger tamper-evident?

Records are append-only and hash-chained so later alteration can be detected during verification. That integrity property does not establish that the original fact, source set, applicability decision or legal judgment was correct.

How do we get started?

Email info@coreidea.cn with your industry and the mandates you care about — labeling, escrow or regulatory radar.

Bring the source — and the workflow it may change.

Map one official version, one accountable role and one implementation path before discussing automation.

All platforms