Pergamum Pulse Rights, Licensing, Citation and Publication Specification
Version 0.1 — Normative Rights and Publication Contract
This specification defines the canonical rights, licensing, citation and publication model for Pergamum Pulse.
It governs copyright ownership, authorship, licences, agreements, permissions, attribution, citation, quotation, data rights, AI-processing rights, publication, withdrawal, revocation, audit and historical reconstruction.
The governing principles are:
Public availability SHALL NOT be interpreted as permission to copy, transform, index, embed, train on, redistribute or publish.
Authorship SHALL NOT automatically be interpreted as copyright ownership.
A right SHALL be represented for the exact intended use, audience, territory, duration, channel and object scope.
An omitted permission SHALL NOT be interpreted as granted.
A public citation SHALL identify the source and preserve the legal, contractual or ownership basis permitting publication.
Rights SHALL follow derived objects, including assertions, embeddings, vector indexes, summaries, translations, projections and public outputs.
1. Scope
This specification applies to every Pergamum Pulse object that stores, transforms, quotes, paraphrases, extracts, indexes, embeds, trains on, redistributes or publishes source-derived content.
2. Rights Object Model
| Object | Prefix | Purpose |
|---|---|---|
| Rights Record | PP-RGT- | Governs rights for one or more objects |
| Rights Evidence | PP-RGE- | Evidence of ownership, licence or permission |
| Licence Record | PP-LIC- | Governs a licence and its terms |
| Agreement Record | PP-AGR- | Governs a contract, assignment or permission |
| Attribution Record | PP-ATR- | Defines required attribution |
| Citation Object | PP-CIT- | Identifies source and citation use |
| Quotation Record | PP-QTE- | Governs exact quotation |
| Publication Rights Record | PP-PRR- | Governs a proposed or active Publication |
| Rights Decision | PP-RGD- | Records approval, restriction or prohibition |
| Rights Finding | PP-RGF- | Records a rights defect or uncertainty |
| Rights Incident | PP-RGI- | Records rights misuse or breach |
| Rights Withdrawal Record | PP-RGW- | Records revocation, expiry or withdrawal |
| Rights Audit Record | PP-RGA- | Records an audit of rights controls |
3. Universal Rights Record
Every source and Knowledge Document SHALL possess or reference a Rights Record.
rights_record:
id: PP-RGT-000001
target_objects:
- PP-SRC-000001
- PP-KD-000001
copyright:
notice: "© 2026 Viroway Ltd. All rights reserved."
holders:
- organisation_id: org.viroway
name: Viroway Ltd
permission_basis:
type: copyright_owner
rights_scope: {}
processing_rights: {}
publication_rights: {}
attribution: {}
validity: {}
evidence: []
status: verified
provenance: {}
Every Rights Record SHALL include identity, target object, copyright holder or explicit unknown state, copyright notice where applicable, permission basis, licence or agreement reference, scope, processing rights, publication rights, attribution, validity, evidence, status and provenance.
4. Copyright Ownership
Authorship metadata SHALL remain separate from ownership metadata.
Employee-created work SHOULD identify employment basis, applicable agreement or policy, work scope, date and provenance.
Contractor-created material SHALL identify contractor, commissioning agreement, assignment clause, assigned rights, retained rights, sublicensing rights and evidence.
Jointly owned works SHALL identify each holder, contribution scope, publication authority, modification authority, sublicensing authority and dispute process.
Public-domain classification SHALL identify legal basis, jurisdiction, effective date, reviewer, evidence and limitations.
5. Viroway-Authored Documents
Every Viroway-authored document SHALL preserve:
- author or contributors;
- commissioning context;
- employee, contractor or assignment basis;
- copyright holder;
- copyright notice;
- copyright year;
- approval state;
- publication eligibility;
- redistribution terms;
- modification terms;
- commercial-use terms;
- AI-processing terms;
- approved source URL;
- internal canonical location;
- provenance.
Recommended baseline:
rights:
copyright_notice: "© 2026 Viroway Ltd. All rights reserved."
copyright_holder:
organisation_id: org.viroway
name: Viroway Ltd
permission_basis:
type: copyright_owner
publication_rights:
public_publication:
state: permitted
redistribution:
state: restricted
processing_rights:
parsing:
state: permitted
structured_extraction:
state: permitted
embeddings:
state: permitted
foundation_model_training:
state: restricted
attribution:
required: true
text: "© 2026 Viroway Ltd"
Ownership does not create Publication eligibility.
6. Licence Records
Every material licence SHALL be represented by a Licence Record.
licence_record:
id: PP-LIC-000001
licence_name: Example Licence
licence_version: "1.0"
licence_url: https://example.invalid/licence
licensor: organisation.example
licensee: org.viroway
effective_from: 2026-01-01
effective_to: 2027-01-01
status: active
Licence classes MAY include all rights reserved, internal corporate licence, standards licence, commercial data licence, open-source licence, open-data licence, Creative Commons, public domain, statutory licence, quotation permission, custom agreement, API terms and website terms.
Licence scope SHALL identify licensed objects, users, organisations, tenants, territories, languages, channels, purposes, duration, modification, sublicensing, redistribution, publication and AI use.
7. Agreement Records
An Agreement Record SHALL identify parties, dates, covered sources, granted rights, retained rights, restrictions, confidentiality, publication, sublicensing, derivative works, AI-processing terms, evidence location, status and provenance.
Agreement types MAY include copyright assignment, contractor assignment, publishing agreement, data licence, standards subscription, API agreement, supplier agreement, permission letter, research agreement, consortium agreement and joint-authorship agreement.
8. Permission Basis
Every material right SHALL identify its basis.
Permitted bases include copyright ownership, employee-created work, contractor assignment, written licence, publication agreement, data licence, open licence, public domain, statutory permission, regulator permission, quotation permission, fair-dealing or fair-use assessment, contract, unknown and prohibited.
A fair-dealing or fair-use assessment SHALL require jurisdiction, purpose, amount used, market effect, transformation assessment, legal reviewer, date, limitations and evidence.
AI SHALL NOT make the final legal determination autonomously.
9. Rights Scope
Rights SHALL be purpose-specific and scope-specific.
rights_scope:
territories:
- eu
audiences:
- internal_staff
organisations:
- org.viroway
purposes:
- internal_analysis
channels:
- internal_docs
effective_from: 2026-01-01
effective_to: 2027-01-01
Derived objects SHALL inherit applicable restrictions from their sources.
Where multiple Rights Records apply, the most restrictive applicable condition SHALL prevail unless an authorised legal decision records another precedence.
10. Processing Rights
Processing rights SHALL be recorded separately.
processing_rights:
storage:
state: permitted
backup:
state: permitted
parsing:
state: permitted
ocr:
state: permitted
translation:
state: permitted_with_conditions
internal_summary:
state: permitted
structured_extraction:
state: permitted
semantic_indexing:
state: permitted
embeddings:
state: permitted_with_conditions
vector_storage:
state: permitted_with_conditions
retrieval_augmented_generation:
state: restricted
model_evaluation:
state: prohibited
fine_tuning:
state: prohibited
foundation_model_training:
state: prohibited
public_generation:
state: restricted
derivative_dataset_creation:
state: prohibited
Permission states SHALL include permitted, permitted with conditions, restricted, prohibited, unresolved, not applicable, expired and revoked.
Parsing permission SHALL remain distinct from reproduction permission.
OCR permission SHALL be evaluated separately where licences restrict copying or digitisation.
Translation permission SHALL identify whether translated output may be stored, internally used, published, modified or redistributed.
Summarisation permission SHALL identify whether summaries may include short excerpts, tables, numerical values, diagrams or derivative interpretation.
Structured extraction SHALL identify whether extracted facts, values, requirements, definitions, code lists, tables, formulas and records may be stored, reused or published.
Semantic indexing permission SHALL not imply public retrieval permission.
Embedding permission SHALL identify model, provider, storage, jurisdiction, tenant, retention, deletion and prohibited downstream use.
RAG permission SHALL identify eligible users, Agents, models, output restrictions, quotation limits, citation requirements, logging, retention and provenance.
Evaluation rights SHALL remain separate from training rights.
Fine-tuning and foundation-model training SHALL default to prohibited unless explicitly permitted.
Public generation SHALL identify whether generated outputs may reveal restricted source content.
Derivative dataset rights SHALL identify permitted fields, transformations, aggregation, anonymisation, redistribution, attribution and database-rights treatment.
11. Publication Rights
Publication rights SHALL be explicit.
publication_rights:
internal_publication:
state: permitted
tenant_publication:
state: restricted
white_label_publication:
state: restricted
public_web_publication:
state: prohibited
commercial_publication:
state: prohibited
redistribution:
state: prohibited
Publication classes MAY include internal, tenant, white-label, partner, regulator, contractual counterparty, public web, public API, report, Academy content, blog, public dataset, certification package and regulatory submission.
Permission to publish internally SHALL NOT imply permission to publish publicly.
Commercial publication rights SHALL be evaluated separately.
Publication in a public Registry SHALL require explicit permission or lawful basis.
12. Attribution
Every source requiring attribution SHALL have an Attribution Record.
attribution:
required: true
text: "Source: Example Publisher, 2026"
source_url: https://example.invalid/source
placement: adjacent_or_references
licence_notice_required: true
modification_notice_required: true
Attribution MAY require author, copyright holder, publisher, title, version, year, source URL, licence name, licence URL, modification statement, access date and disclaimer.
Attribution SHALL remain associated with quoted content, paraphrases, data, images, figures, tables, derivatives and generated exports.
13. Citation Objects
Every material citation SHALL be represented as a Citation Object.
citation:
id: PP-CIT-000001
source_object: PP-SRC-000001
source_capture: PP-CAP-000001
source_fragment: PP-SF-000001
source_url: https://example.invalid/source
citation_type: paraphrase
rights_record: PP-RGT-000001
attribution_record: PP-ATR-000001
publication_permission:
state: permitted_with_conditions
provenance: {}
Citation types MAY include reference only, quotation, paraphrase, translated quotation, data citation, figure citation, table citation, code citation, legal citation, standard citation, API citation and dataset citation.
A citation SHALL include an exact locator where available.
Locator types MAY include page, clause, article, paragraph, table, row, cell, figure, diagram, dataset record, API field, code block and timestamped segment.
A public citation SHOULD link to the official source where available.
A restricted citation MAY use a controlled internal source reference.
Access date SHOULD be recorded for mutable web and API sources.
Citation SHALL preserve source version or edition.
14. Quotations
Every quotation SHALL identify:
- Quotation Record;
- exact Source Fragment;
- quoted text or digest;
- quotation length;
- source version;
- language;
- rights basis;
- attribution;
- permitted audience;
- publication status;
- provenance.
Quotation limits SHALL be represented where applicable.
quotation_limit:
max_words: 25
per_source: true
A quotation SHALL NOT materially misrepresent source context.
Translated quotations SHALL identify source text, translation, translator or model, review, controlling language, rights and provenance.
Truncation SHALL be indicated where it could affect meaning.
15. Paraphrases and Summaries
A paraphrase or summary SHALL identify source, locator, transformation type, source coverage, reviewer, controlling source, rights basis, publication permission and provenance.
A paraphrase SHALL NOT be represented as verbatim source text.
A summary SHALL NOT conceal material limitations relevant to the claim.
16. Data and Database Rights
Data use SHALL preserve:
- dataset identity;
- dataset version;
- rights holder;
- licence;
- database rights;
- record scope;
- extraction query;
- transformation;
- aggregation;
- attribution;
- publication rights;
- provenance.
Where records have distinct rights, record-level restrictions SHALL be preserved.
Large-scale extraction SHALL be assessed separately from individual factual use.
Aggregation SHALL not be assumed to remove rights restrictions.
Derived indicators SHALL identify source datasets, formulas, transformations, rights and publication conditions.
17. Images, Figures, Tables and Media
Media objects SHALL be rights-reviewed independently where required.
Every media object SHALL identify media identity, source, creator, copyright holder, licence, permitted use, modification rights, attribution, publication permission, accessibility requirements and provenance.
Extracted figures SHALL preserve captions, labels, source locator and rights.
Reproduced tables SHALL preserve source, structure, units, footnotes, rights and attribution.
Screenshots SHALL identify captured interface or document, source, date, rights, redaction, personal data and publication permission.
Logos, certification marks and trademarks SHALL be governed separately from copyright where required.
18. Standards and Restricted Publications
Licensed standards SHALL identify:
- standards body;
- licence holder;
- purchased or licensed copy;
- permitted users;
- access restrictions;
- reproduction restrictions;
- quotation limits;
- paraphrase permission;
- structured-extraction permission;
- embedding permission;
- training permission;
- public-rendering prohibition;
- retention;
- deletion;
- audit requirements.
A restricted standard SHALL NOT be reproduced publicly unless permission exists.
Metadata, identifiers and controlled paraphrases MAY be used only where permitted.
19. Regulatory and Public-Authority Sources
Public-authority sources SHALL still receive a Rights Record.
The record SHALL distinguish legal authority, copyright status, database rights, reuse licence, attribution, official-source requirements, modification restrictions, public-sector-information terms and jurisdiction.
Legal authority SHALL NOT be confused with unrestricted reuse rights.
20. Scientific and Research Sources
Scientific sources SHALL identify publisher, authors, DOI, licence, open-access status, version, preprint or version-of-record status, supplementary-data rights, figure rights, text-mining rights and retraction or correction state.
Open access SHALL NOT be assumed without licence evidence.
21. Supplier and Manufacturer Sources
Supplier and manufacturer sources SHALL identify publisher, product or model scope, document version, confidentiality, contractual restrictions, public availability, extraction rights, publication rights, trademark restrictions, warranty disclaimers and provenance.
A manufacturer manual may support technical assertions without granting reproduction rights.
22. Tenant and White-Label Rights
Tenant- or white-label-provided content SHALL identify contributing party, ownership claim, licence to Viroway, permitted processing, cross-tenant prohibition, promotion eligibility, Publication prohibition or permission, retention, deletion, termination and provenance.
Promotion to global knowledge SHALL require rights confirmation, confidentiality review, anonymisation where needed, permission for global reuse, review, approval and provenance.
Termination SHALL trigger review of retained source bytes, derived assertions, embeddings, vectors, globalised knowledge, Publications and historical records.
23. Rights Inheritance
Derived objects SHALL inherit applicable rights from all material source objects.
Source Rights
↓
Capture Rights
↓
Document Rights
↓
Section or Fragment Overrides
↓
Assertion Rights
↓
Entity or Mapping Rights
↓
Embedding or Projection Rights
↓
Publication Rights
A narrower fragment-level restriction SHALL prevail.
Where an object derives from multiple sources, the most restrictive applicable right SHALL prevail unless an authorised Rights Decision records another treatment.
Transformation, aggregation, translation or paraphrase SHALL NOT silently remove applicable rights.
24. Rights Decision
A Rights Decision SHALL identify:
- Rights Decision Identifier;
- object or proposed use;
- Rights Records considered;
- legal basis;
- decision;
- conditions;
- authority;
- effective time;
- expiration;
- review date;
- provenance.
Decision states MAY include permitted, permitted with conditions, restricted, prohibited, unresolved, deferred, expired, revoked and superseded.
25. Rights Gate
Every material use SHALL pass a Rights Gate.
The Rights Gate SHALL evaluate:
- source identity;
- object identity;
- intended use;
- audience;
- territory;
- channel;
- duration;
- processing type;
- publication type;
- licence;
- agreement;
- attribution;
- confidentiality;
- tenant scope;
- white-label scope;
- expiration;
- revocation;
- provenance.
Gate outcomes MAY include:
- Pass;
- Pass with Conditions;
- Internal Use Only;
- Restricted Audience;
- Legal Review Required;
- Additional Permission Required;
- Block;
- Quarantine;
- Unable to Determine.
The Gate SHALL block where ownership is unresolved and required, licence absent, permission prohibited, rights expired or revoked, attribution cannot be satisfied, source confidential, tenant scope violated, restricted text exposed, or required agreement evidence unavailable.
26. Publication Package
Every material Publication SHOULD possess a Publication Package containing:
- Publication identity;
- audience;
- channel;
- source objects;
- Citation Objects;
- Quotation Records;
- Rights Records;
- Rights Decisions;
- attribution;
- redactions;
- licence notices;
- review;
- approval;
- release time;
- provenance.
publication_package:
id: PP-PUB-000001
sources:
- PP-SRC-000001
citations:
- PP-CIT-000001
rights_records:
- PP-RGT-000001
rights_decisions:
- PP-RGD-000001
audience: public
channel: web
status: approval_pending
Publication approval SHALL remain separate from document approval, semantic approval, Rights Record verification and technical review.
A Publication SHALL NOT claim more than the source, evidence, authority and rights support.
27. Publication Review
Publication review SHALL assess:
- source accuracy;
- citation completeness;
- attribution completeness;
- rights;
- scope;
- confidentiality;
- personal data;
- trademark and mark use;
- public-claim accuracy;
- current source status;
- current licence status;
- correction and withdrawal pathway.
Review outcomes MAY include Approved, Approved with Conditions, Restricted Audience, Correction Required, Rights Review Required, Legal Review Required, Rejected and Withdrawn.
28. Release and Verification
Release SHALL preserve approving authority, release time, release version, public URL, digest, rights status, citations, verification reference and provenance.
A public verification record SHOULD expose Publication identity, version, issue time, current status, source references, copyright, licence and correction or withdrawal status.
29. Correction, Restatement, Supersession and Withdrawal
The Constitutional Publication Framework SHALL govern public lifecycle actions.
Correction SHALL preserve the original Publication and identify corrected content.
Restatement SHALL identify materially revised content and reason.
Supersession SHALL identify successor Publication.
Withdrawal SHALL identify Publication, reason, authority, effective time, affected citations, affected downstream uses, public notice and provenance.
A rights-driven withdrawal MAY be required where a licence expires, permission is revoked, ownership is disputed, confidential content was published, attribution is defective, quotation exceeds permission or mark use is invalid.
30. Expiration and Revocation
Expiration or revocation SHALL trigger affected-object analysis over:
- Source Captures;
- Knowledge Documents;
- Source Fragments;
- Assertions;
- Entities;
- Mappings;
- embeddings;
- vector indexes;
- prompts;
- caches;
- model-evaluation datasets;
- fine-tuning datasets;
- derived datasets;
- Projection Manifests;
- Publications;
- public APIs;
- tenant and white-label outputs.
Historical preservation SHALL distinguish prior lawful use, future prohibited use, deletion requirements, retention requirements, Legal Hold, archive-only state and public withdrawal requirements.
A Rights Withdrawal Record SHALL identify affected Rights Record, reason, authority, effective time, objects affected, required actions, completion status and provenance.
31. Deletion and Unlearning
Where rights require deletion, the process SHALL evaluate:
- source bytes;
- transformed documents;
- fragments;
- assertions;
- embeddings;
- vector indexes;
- caches;
- derivative datasets;
- model-training datasets;
- fine-tuned models;
- generated outputs;
- backups;
- archives;
- Legal Holds.
Where model training occurred and deletion is required, the system SHALL record model, training dataset, affected records, technical feasibility, unlearning method, retraining requirement, residual risk, verification and provenance.
A destruction receipt SHALL preserve object, authority, basis, method, time, verifier, exceptions and provenance.
32. Rights Conflicts
Conflicts MAY include inconsistent licences, ownership disputes, agreement conflicts, territorial conflicts, publisher conflicts, open-licence incompatibility, attribution conflicts, database-rights conflicts, tenant-rights conflicts and Publication-rights conflicts.
A conflict SHALL preserve competing records, evidence, scope, legal review, decision, unresolved limitations and provenance.
The system SHALL NOT silently choose the least restrictive interpretation.
33. Rights Incidents
Rights incidents MAY include:
- unauthorised publication;
- unauthorised redistribution;
- excessive quotation;
- missing attribution;
- expired licence use;
- revoked-rights use;
- unauthorised embedding;
- unauthorised model training;
- cross-tenant disclosure;
- confidential source exposure;
- unauthorised derivative dataset;
- invalid certification mark use.
Every Rights Incident SHALL identify Incident Identifier, affected source, affected object, audience, tenant or white-label operator, detection time, severity, containment, notification, correction, withdrawal, root cause, remediation and provenance.
34. Rights Assurance and Audit
Rights assurance MAY evaluate:
- Rights Record completeness;
- ownership evidence;
- licence validity;
- permission scope;
- attribution;
- processing controls;
- embedding controls;
- training controls;
- Publication controls;
- withdrawal;
- deletion;
- historical reconstruction.
A Rights Audit SHALL identify audit identity, scope, criteria, auditor, independence, sample, evidence, Findings, conclusion, remediation and provenance.
Findings MAY include missing Rights Record, unresolved ownership, expired licence, unauthorised processing, missing source link, missing attribution, Publication beyond scope, embedding beyond scope, training beyond scope, incomplete withdrawal, incomplete deletion and incomplete provenance.
35. AI Agent Boundaries
AI Agents MAY classify rights metadata, identify likely licence text, compare agreement clauses, flag risks, generate draft citations and attribution, identify affected objects and support audit sampling.
AI Agents SHALL NOT independently:
- determine copyright ownership;
- grant permission;
- decide fair use or fair dealing;
- waive attribution;
- approve public Publication;
- approve model training;
- resolve ownership disputes;
- override a Rights Gate;
- destroy evidence;
- withdraw a Publication.
36. HECATE Validation
HECATE SHALL validate objective structure including:
- Rights Record identity;
- target-object relationship;
- copyright holder metadata;
- permission basis;
- licence identity;
- agreement identity;
- validity;
- rights scope;
- processing-rights fields;
- Publication-rights fields;
- attribution;
- Citation Object;
- source locator;
- source URL or controlled reference;
- Rights Decision;
- Rights Gate outcome;
- Publication Package completeness;
- expiration;
- revocation;
- withdrawal;
- destruction receipt;
- Module lineage;
- Component lineage;
- provenance.
HECATE SHALL NOT create copyright ownership, create a licence, grant permission, determine disputed legal meaning, decide fair use autonomously, waive contractual restrictions, approve public Publication or infer training permission from public access.
37. Module and Component Lineage
Every material rights path SHALL identify:
- accountable Module;
- Rights Registry Component;
- Source Capture Component;
- transformation Component;
- retrieval Component;
- embedding Component;
- model-processing Component;
- Publication Component;
- archive Component;
- affected Runtime Components;
- affected tenant or white-label context.
No orphan Component lineage is permitted.
38. Historical Rights Reconstruction
A historical query SHALL identify:
- source;
- source version;
- Rights Record version;
- licence version;
- agreement version;
- permission state;
- scope;
- attribution requirement;
- Citation Object;
- Publication;
- validity at target time;
- later expiration or revocation;
- provenance.
Historical reconstruction SHALL distinguish what was permitted then, what is permitted now, what was published then and what was later corrected or withdrawn.
Current rights SHALL NOT be applied retroactively without legal basis.
39. Conformance Levels
39.1. Level 1 — Rights-Identified
The object has copyright holder or explicit unknown, permission basis, licence or agreement reference, status and provenance.
39.2. Level 2 — Rights-Governed
It additionally has scope, processing rights, Publication rights, attribution, validity, evidence and review.
39.3. Level 3 — Publication-Ready
It additionally has complete citations, Rights Decisions, Publication Package, approved audience and channel, no blocking Findings and HECATE validation.
39.4. Level 4 — Historically Assured
It additionally has immutable rights history, expiration and revocation tracking, withdrawal controls, deletion and archive evidence, historical reconstruction and assurance evidence.
40. Conformance Fixtures
Implementations SHOULD provide fixtures for:
- Viroway-owned document;
- employee-authored document;
- contractor-authored document with assignment;
- contractor-authored document without assignment;
- jointly owned work;
- public-domain source;
- public-domain claim without evidence;
- all-rights-reserved source;
- Creative Commons source;
- standards licence;
- commercial dataset licence;
- territorial restriction;
- language restriction;
- expired licence;
- revoked licence;
- unresolved ownership;
- metadata-only use;
- parsing permitted but reproduction prohibited;
- OCR prohibited;
- translation permitted with conditions;
- embeddings permitted internally;
- public RAG prohibited;
- model evaluation permitted but training prohibited;
- fine-tuning prohibited;
- derivative dataset prohibited;
- valid citation;
- citation without locator;
- citation without source URL;
- quotation within limit;
- quotation exceeding limit;
- paraphrase with attribution;
- figure reuse prohibited;
- table reproduction permitted;
- valid public Publication Package;
- Publication beyond rights scope;
- tenant content promoted without permission;
- rights-driven withdrawal;
- deletion propagation;
- incomplete embedding deletion;
- historical-rights reconstruction;
- complete Rights Audit.
41. Migration and Compatibility
Specification revisions SHALL identify source version, target version, changed rights fields, changed permission states, changed licence types, changed citation fields, changed Publication requirements, migration rules, compatibility, affected objects and provenance.
Migration SHALL NOT infer permission, infer ownership, widen rights, discard restrictions, overwrite historical Rights Records, delete unresolved conflicts or treat unknown as permitted.
42. Security and Confidentiality
Rights records and agreement evidence MAY themselves be confidential.
Controls SHALL include least privilege, legal-team access, tenant isolation, white-label isolation, encryption, access logging, redaction, export restriction, retention, Legal Hold and incident response.
A public rights summary MAY expose copyright holder, licence name, attribution, Publication status and public source link.
It SHALL NOT expose confidential agreement terms unless authorised.
43. Conformance Requirements
An implementation conforms to this specification where it:
- assigns a Rights Record to every source and Knowledge Document;
- identifies copyright holder or explicit unresolved state;
- separates authorship from ownership;
- preserves employee and contractor ownership basis;
- governs joint ownership;
- preserves public-domain evidence;
- applies copyright metadata to Viroway-authored documents;
- links Viroway documents to approved legal information;
- distinguishes ownership from Publication eligibility;
- represents licences as versioned objects;
- represents agreements as governed objects;
- identifies permission basis;
- preserves rights scope by territory, audience, purpose, channel, duration and object;
- applies the most restrictive applicable rule;
- distinguishes storage, parsing, OCR, translation, summarisation, extraction, indexing, embeddings, RAG, evaluation, fine-tuning, training, public generation and derivative-dataset rights;
- defaults fine-tuning and foundation-model training to prohibited unless explicitly permitted;
- represents Publication rights separately from processing rights;
- preserves attribution requirements;
- represents citations as first-class objects;
- preserves exact source locators;
- preserves source URLs or controlled source references;
- preserves source versions and access dates where relevant;
- governs quotations and quotation limits;
- distinguishes quotation from paraphrase and summary;
- governs dataset and database rights;
- governs images, figures, tables, screenshots, logos and marks;
- governs restricted standards;
- distinguishes legal authority from reuse rights for regulatory sources;
- governs scientific, supplier and manufacturer sources;
- preserves tenant and white-label rights boundaries;
- prevents unauthorised global promotion;
- propagates rights restrictions to derived objects;
- governs multi-source rights inheritance;
- records Rights Decisions;
- evaluates intended use through a Rights Gate;
- blocks uses with unresolved or prohibited rights;
- assembles Publication Packages;
- separates Publication approval from semantic and document approval;
- prevents claims from exceeding source rights and evidence;
- preserves release and verification metadata;
- governs correction, restatement, supersession and withdrawal;
- performs affected-object analysis after expiration or revocation;
- governs deletion and model-unlearning obligations;
- preserves destruction receipts;
- preserves rights conflicts as explicit states;
- manages Rights Incidents;
- supports rights assurance and audit;
- prevents AI Agents from granting rights or overriding Rights Gates;
- validates objective structure through HECATE;
- preserves Module lineage;
- preserves Component lineage;
- reconstructs historical rights state;
- defines conformance levels;
- supports conformance fixtures;
- preserves security and confidentiality;
- never interprets unknown or omitted permission as granted.
44. Foundational Principle
Pergamum Pulse SHALL preserve not only what knowledge says, but who owns it, who may use it, how it may be transformed, where it may be published, how it must be attributed and when those rights begin, change or end.
Public access is not permission. Authorship is not always ownership. Citation is not reproduction authority. Translation is not licence expansion. Embedding is not rights removal. Aggregation is not automatic freedom from database rights. AI processing is not exempt from copyright or contract.
Every source-derived object SHALL retain its applicable rights lineage. Every public output SHALL preserve source, attribution and lawful basis. Every revocation SHALL propagate to affected documents, embeddings, models, projections and Publications. Every rights state SHALL remain historically reconstructable.
By making rights, licences, agreements, citations, attribution and Publication controls first-class governed objects, Pergamum Pulse can scale global knowledge acquisition and reuse while protecting Viroway, its partners, tenants, source owners and the integrity of ZAYAZ.