Eolas · Togra Log in →
Eolas · Using Togra

Cearta (Rights) — module user guide

Last verified 8 Jun 2026


# Cearta (Rights) — User Guide

The rights, revenue and reporting module of Togra: how it manages a finished title's exploitation, statutory talent reporting, the recoupment waterfall and the collection-account loop — surface by surface, and how it connects to the money and the production.


1. What Cearta is for

A film or TV programme keeps generating rights, revenue and obligations long after the shoot wraps. Someone has to license it territory by territory without double-selling, report royalties to the talent the law now requires, run the recoupment waterfall, track guild residuals, clear the music, keep the chain of title audit-ready, and reconcile what the collection agent reports back. Cearta is where all of that lives. It is Togra's rights module — the business-affairs and revenue home for a title from delivery through its commercial life.

Its job has four strands:

  • Statutory reporting — the DSM Article 19 transparency reports producers owe their writers, directors and performers (jurisdiction-aware, with a recipient query/objection workflow and an audit-readiness view).
  • Revenue & waterfall — the net-profit waterfall calculator, residual obligations, the CAM (collection-account) settlement loop, and per-project sales reports.
  • The rights cataloguechain of title, rights windows (territory × media × window), slate-wide avails and conflict detection.
  • Clearance & deliverymusic cue sheets and licences, plus secure, NDA-gated document sharing.

Cearta is the outward-facing layer: it reports to talent, collection agents, funders and buyers. The revenue it reports flows in from the collection-statement importer (which posts to the revenue ledger in Cuntasaíocht); the pre-sales and distribution it summarises come from Airgead financing; the music cue sheets and releases it owns are compiled on the Bordáil floor at wrap. (See section 5.)


2. The rights lifecycle, end to end

How the surfaces line up across a title's commercial life:

  1. Establish the rightsChain of title records IP provenance from the underlying option (in Forbairt) through to the producer; the music register clears every cue.
  2. Define what you can sellRights windows record each licence (territory × media × window); Avails shows the slate-wide open-market grid; Conflicts flags any overlap before you double-license.
  3. Sell it → pre-sales and distribution deals (raised as finance in Airgead) feed the per-project Sales report; a CAM / sales-agent handoff pack hands a collection agent everything they need, with a return-statement spec.
  4. Collect and distribute → when a collection statement is ingested, CAM settlement raises the draw-down invoice and the downstream remittance advices; revenue posts to the ledger.
  5. Run the waterfallNet profits computes the recoupment waterfall to the net-profit participants; Residuals tracks the guild obligations that ride on revenue.
  6. Report to talentTransparency generates the Article 19 reports per recipient and jurisdiction; Queries handles their objections; Compliance tracks coverage and overdue filings.
  7. Report to funders / share securelyDiversity for funder diversity reporting; Secure shares for NDA-gated delivery of audit packs and deal memos.

The loop closes on itself: the handoff pack's return spec is the inverse of the collection-statement importer, so statements ingest cleanly → revenue → the waterfall → Article 19 reporting.


3. How the module is laid out

The Cearta sub-nav:

  • Home — rights overview.
  • Transparency (Article 19): Transparency · Queries · Compliance.
  • Revenue & waterfall: Settlement (CAMA) · Monetization · Net profits · Residuals · Sales report.
  • Rights catalogue: Chain of title · Windows · Conflicts · Avails.
  • Clearance & reporting: Music · Diversity · Secure shares.

Most surfaces are project-scoped; several are slate-wide (Avails, Conflicts, the transparency compliance view, Diversity).


4. The surfaces in detail

Transparency — Article 19

Transparency (transparency.php) — the flagship: the DSM Article 19 / SI 567/2021 reports a producer owes the writers, directors and performers on a title. It's jurisdiction-aware (per-recipient variants), aggregates revenue per contract, and produces a per-recipient report a talent or their agent opens via a tokenised link (r.php) with no login. A worker-level aggregator rolls a person's reports across the slate. Queries (transparency-queries.php) — the recipient query/objection workflow on those reports (open / answered / closed threads). Compliance (transparency-compliance.php) — audit-readiness: coverage / open / acknowledged rates and overdue Article 19 filings across the slate.

Revenue & waterfall

Monetization (monetization-hub.php) — the per-title money position in one place: gross collected (broken down by exploitation type) and net receipts vs the production budget, the recoupment position (how much is still recouping) and net-profit participant distributions so far, residuals outstanding/overdue, and the distribution deals. A read-only roll-up that links to each editor; it reads the existing waterfall / revenue-ledger / residuals / distribution engines (no new storage). Net profits (net-profits.php) — the recoupment waterfall calculator: banded/capped/overage-and-reserve/pari-passu/per-scope mechanics down to the net-profit participants. CAM settlement (cama-settlement.php) — after a collection-agent statement is ingested, raises the draw-down invoice to the collection agent and the downstream remittance advices. Residuals (residuals.php) — guild residual obligations (beneficiary, role, guild). Sales report (sales-report.php) — the per-project sales + distribution snapshot (pre-sales, rights windows, revenue, waterfall, deliverables), exportable to DOCX + PDF. The CAM / sales-agent handoff pack (reached from a project's rights view) bundles chain of title, the avails map, distribution + pre-sales, the recoupment schedule, the net-profit register and residual obligations, plus a return-statement spec — its own Eolas doc has the detail.

The rights catalogue

Chain of title (chain-of-title.php) — the title chain and IP provenance, from the underlying-rights option through to the producer, with the clearance checklist a financier/auditor expects. Windows (rights-windows.php) — the rights windows and options: each licence as territory × media × window. Conflicts (rights-conflicts.php) — the slate-wide conflict report that flags any overlapping window before you double-license. Avails (rights-overview.php) — the slate-wide rights overview: every licence across all projects bucketed exploited / expiring / available, with the open-market avails grid.

Clearance & reporting

Music (music-clearances.php) — music clearances plus the cue sheet (with sync / master licence clearance and cue-sheet export); the cue sheet is delivery-critical and is also reachable from the Bordáil wrap workflow (same register). Diversity (diversity-hub.php) — the per-production diversity home, pulling every diversity surface into one place: the BFI Diversity Standards status (with links to edit the standards and publish the BFI pack + its history), the anonymous crew self-reports aggregate (diversity-aggregate.php — crew opt in from their worker portal; buckets under 5 masked), the statutory diversity status, the Screen Ireland Diversity & Inclusion narrative where an SI application exists, and a cast gender snapshot (S481 Tab Z). The underlying data stores stay separate and single-purpose; the hub just unifies the navigation. Secure shares (shares.php) — tokenised secure document delivery (scripts, deal memos, audit packs) with an optional password + NDA gate, viewed/acknowledged tracking, and revocation.


5. Cearta and the rest of Togra

Cearta is the outward-facing rights/revenue hub; it draws from and feeds its neighbours:

  • Forbairt → Cearta. The underlying-rights option established in development (canonical in Forbairt IP) is the head of the chain of title; Cearta's Windows tab also references the option for continuity.
  • Bordáil → Cearta. Music cue sheets and releases are compiled on the production floor at wrap and are rights/clearance deliverables — cue sheets are canonical here, surfaced in Bordáil's wrap workflow. Diversity self-reports are captured at onboarding in Bordáil and aggregated here.
  • Airgead → Cearta. Pre-sales and distribution deals are raised as finance sources in Airgead; Cearta's sales report and avails summarise them. The financing recoupment corridor (Airgead) and the revenue waterfall (Cearta) are the two ends of the same recoupment story.
  • Cearta ↔ Cuntasaíocht. Revenue arrives via the collection-statement importer, which posts to the revenue ledger; CAM settlement's draw-down invoice and remittances are book-of-record events. So the waterfall and Article 19 reports are computed on real, posted revenue.
  • Sharing surfaces. Cearta's NDA-gated Secure shares sits alongside Forbairt's no-login Guest review and leak-traceable Distribution — three delivery mechanisms for three stages (rights/audit packs vs dev review vs finished-film PDFs).

Deadline nudges. Cearta's obligations surface in the approvals inbox: overdue Article 19 filings, open transparency queries, rights-window expiries and slate conflicts.

Audit note (2026-06-07): the Cearta surfaces are correctly scoped to rights, revenue and outward reporting, and internally coherent. The cross-module overlaps are all single-page dual-surfacing with clear canonical homes: rights options are canonical in Forbairt (development IP) and only referenced from the Windows tab; music cue sheets are canonical here and reached from the Bordáil wrap workflow; pre-sales / distribution are canonical in Airgead financing and summarised here. No surface needed to move.

6. How this makes rights easier for a production company

  • Statutory talent reporting, handled. Article 19 reporting is a legal obligation that is painful by hand; Cearta generates the per-recipient, jurisdiction-aware reports, serves them by tokenised link, runs the query/objection workflow, and tracks coverage and overdue filings — so a producer can prove compliance.
  • You never double-sell. Rights windows + the avails grid + the conflict report mean every licence is recorded as territory × media × window, and any overlap is flagged before a contract is signed.
  • The waterfall is transparent. Net profits computes recoupment to the participant, on real posted revenue, so net-profit statements and residual obligations are defensible.
  • The collection loop closes. The handoff pack tells the CAM exactly how to report back; the return spec is the inverse of the importer, so statements ingest with no manual column-mapping, post as revenue, and flow into the waterfall and Article 19 reports.
  • Chain of title is audit-ready. Provenance from the underlying option through clearances to the producer is one record — what a financier, auditor or buyer asks for.
  • Sharing without leaks. NDA-gated, tracked, revocable secure shares for the audit packs and deal memos that can't just be emailed.

7. Worked examples

A. An Article 19 report. From Transparency, generate the per-recipient reports for a title's writers/directors/performers; each recipient opens theirs via a tokenised link with no login; if they object, the thread runs in Queries; Compliance shows your slate-wide coverage and any overdue filings.

B. Licensing a territory. Record the licence in Windows (territory × media × window); Conflicts confirms it doesn't overlap an existing grant; Avails updates the open-market grid so you can see what's still sellable.

C. Revenue in, waterfall out. A collection-agent statement is ingested (posting revenue to the ledger); CAM settlement raises the draw-down invoice and remittances; Net profits runs the waterfall to the participants; Residuals picks up the guild obligations — and the Transparency reports reflect the new revenue.

D. Delivering the music. Clear every cue in Music (sync + master), compile the cue sheet (shared with the Bordáil wrap workflow), and export it — delivery-critical, and now part of the chain-of-title record.


This guide reflects the Cearta module as shipped. The CAM handoff pack and Article 19 reporting each have their own Eolas detail; the Airgead and Cuntasaíocht guides cover the financing and book of record that revenue flows through, and the Bordáil guide covers the production that compiles the cue sheets and releases.

Sources

  • · lib/module_subnav.php (the cearta block — surface list + authoritative descriptions)
  • · transparency.php · worker-transparency.php · r.php (Article 19 reporting + token view)
  • · net-profits.php · cama-settlement.php · residuals.php · sales-report.php (revenue + waterfall)
  • · chain-of-title.php · rights-windows.php · rights-overview.php · rights-conflicts.php (rights catalogue)
  • · lib/handoff_pack.php (the CAM / sales-agent handoff pack)