STANDARD B

Production Standard

Reference: FIDES-RFC-002
Status: Active Standard
Target Audience: Publishers, CMS Developers, Data Journalists

1. Objective

The Production Standard (Standard B) defines the technical requirements for creating "Fides-Ready" information assets. By adhering to this standard, publishers ensure their content is machine-readable, verifiable, and eligible for high Trust Scores in the Global Source Index.

2. Metadata Specification (JSON-LD)

All compliant pages MUST inject a structured data block in the<head> section. This metadata allows verification nodes to cryptographically bind the content to its creator.

<script type="application/ld+json">
{
  "@context": "https://fidesstandard.com/ns/v1",
  "@type": "NewsArticle",
  "headline": "Global Market Analysis Q3",
  "publisher": {
    "@type": "Organization",
    "name": "Times Commerce",
    "fidesSourceId": "FS-SRC-042"
  },
  "provenance": {
    "c2pa_manifest": "https://verify.contentauthenticity.org/inspect?url=...",
    "ipfs_cid": "ipfs://bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3jhafm",
    "encodingFormat": "application/pdf",
    "contentHash": "sha256-7f83b1657ff1fc53b92dc18148a1d65dfc2d4b1..."
  }
}
</script>

*Integration Tip: By including a c2pa_manifest, Fides provides a trust-layer audit for hardware-signed media.

3. Industry Standard Interoperability

Fides Standard is designed to complement existing provenance frameworks, acting as the high-level validation layer.

Trust Layer for C2PA

While C2PA secures the hardware-level origin of media, Fides provides theReputation Layer. We audit the identity of the entity signing the C2PA manifest.

Decentralized Persistence

All Fides-Ready assets supportContent Addressing. By referencing an IPFS CID, we ensure the underlying information remains accessible and tamper-proof.

Schema.org Extension

Fides Standard v1.0 extends standard Schema.orgNewsArticle objects, making our trust markers natively readable by search engines and AI agents.

4. Content Hashing & Immutability

To prevent retroactive editing (stealth edits) without audit trails, the content body must be hashed upon publication.

  • Algorithm:SHA-256 (Secure Hash Algorithm 256-bit).
  • Scope:The hash must cover the headline, body text, and publication timestamp.
  • Submission:The hash must be submitted to the Fides Registry API within 60 minutes of publication to mint the Asset ID.

5. Citation Integrity Rules

A high Trust Score requires robust provenance. The following citation rules apply:

  • Primary Sources:At least one citation must link to a primary data source (e.g., government report, academic paper, raw dataset).
  • Permalinks:Citations should use persistent identifiers (DOIs) or archived snapshots (e.g., Wayback Machine) where possible to prevent link rot.
  • Self-Referencing:Circular reporting (citing your own unverified articles) is penalized by the algorithm.
← Return to Standard Overview