license: cc-by-4.0
task_categories:

• text-generation
• question-answering
• text-classification
  language:
• ms
• en
  tags:
• constitutional-ai
• arifos
• federation
• conflict-resolution
• judiciary
• skill-mesh
• dispute-resolution
• governance
• kernel-audit
• f1-f13
• bahasa-melayu
• malaysian-llm
  size_categories:
• n<1000
  pretty_name: CCC — Conflict Registry (Judiciary Layer of arifOS Federation)
  configs:
• config_name: conflict_registry
  default: true
  data_files:
  • split: train
    path: registry/train-00000-of-00001.parquet
• config_name: historical_probe_archive
  data_files:
  • split: train
    path: data_archive/train-00000-of-00001.parquet

CCC — Conflict Registry (Judiciary Layer)

arifOS Federation Judiciary · AAA=Constitution · BBB=Audit · CCC=Conflict Resolution

What This Is

CCC is the judiciary layer of the arifOS Federation — a governed conflict registry that records, classifies, and tracks the resolution of disputes across the federation's 7 organs and 555+ skills.

Conflict is not a defect. Unrecorded conflict is.

Federation Context

         Arif (Human Sovereign — F13)
                │
                ▼
        arifOS (Constitutional Kernel)
        F1–F13 floor enforcement
                │
    ┌───────┬───┴───┬───────┬───────┐
    ▼       ▼       ▼       ▼       ▼
  AAA     A-FORGE  WELL    WEALTH  GEOX
 Const.   Exec.   Vitality Capital  Earth
    │
    ▼
  CCC ← YOU ARE HERE (Judiciary)

Registry Structure

Each conflict record follows this schema:

Current Registry (12 records)

By Severity

By Status

By Domain

Key Precedents

1. CCC-SKILL-ID-001/002: Skill identity conflicts resolve by picking the larger/more-complete copy as canonical, converting the other to a pointer-stub.
2. CCC-PROTO-VIOL-001 (P1): The Grok incident — agent commits governance mutation without authority envelope. Established: RESOLVED=TRUE, PATCH_READY=TRUE, AUTHORIZED=FALSE, MUTATION=BLOCKED.
3. CCC-RES-CONT-001: Concurrent state file writes → flock + append-only path. Schema versioning enforced.
4. CCC-ROUTE-AMB-001: Re-measurement corrected false positive. Rule: counts from symlink-heavy trees must specify dedup scope.

Datasets

How to Use

from datasets import load_dataset

ds = load_dataset("ariffazil/CCC", split="train")
# Filter open conflicts
open_conflicts = ds.filter(lambda x: x["status"] in ("DETECTED", "REGISTERED", "HEARING"))
# Filter by severity
critical = ds.filter(lambda x: x["severity"] == "P1")

History

• 2026-06-07: CCC v1 — Anomalous Contrast experiment (ILMU direct vs arifOS kernel)
• 2026-09-16: Skill mesh conflict register — 4 true conflicts identified
• 2026-09-19: CCC v2 — Conflict Registry (judiciary layer) seeded with 12 records

License

CC-BY-4.0

Citation

@misc{ccc_conflict_registry_2026,
  title={CCC — Conflict Registry (Judiciary Layer of arifOS Federation)},
  author={Muhammad Arif bin Fazil},
  year={2026},
  howpublished={\\url{https://huggingface.co/datasets/ariffazil/CCC}},
  note={arifOS Federation Judiciary}
}

Provenance, Scope & Revision Pinning

• License (observed metadata): CC BY 4.0. Author-declared, not independently verified.
• Series license gradient: Across AAA–FFF the licenses follow a functional split (law / evidence / tooling). Whether model weights trained on this corpus inherit any license obligation is an open legal question — no claim is made here. Seek legal review before training use.
• Download counts on this page are repository download events (deduplicated per IP per time window) — not unique users, not complete corpus copies, not training uses.
• Cite by revision: pin ariffazil/CCC@<commit-sha> in every downstream claim. Unpinned citations point at a moving target.
• Epistemic status: labels are builder-declared.

Dataset Structure (explicit dual configuration)

This repository ships TWO distinct dataset surfaces, now exposed as explicit Viewer configurations:

Historical note: prior to 2026-10-14 the archive surface was undeclared in configs (CONFIGURATION_SHADOWING);
it is now discoverable via the Viewer config dropdown.

Data Sources and Provenance

Registry rows: federation conflict records. Archive rows: raw A/B probe receipts comparing
direct-model vs kernel-mediated paths (2026-06 run). 19 of 32 archive columns are reserved kernel
fields, null on 8/16 rows — documented-reserved, not corruption.

Parse Failure vs Semantic Truth (CCC-v1)

CCC-v1 records a parser-contract mismatch: the kernel envelope expected structured JSON while the
substrate returned free-form prose, producing HOLD. This is L02A_PARSEABILITY failure; L02B_TRUTH_VERACITY
is NOT_EVALUATED for those rows. HOLD here does NOT mean the model content was semantically proven wrong.

Personal and Sensitive Information

Automated scan 2026-10-14: no emails, no credentials, no real phone numbers.

Biases and Limitations

• Archive rows capture a mediation-era run with known parser-contract limitations; treat archive
  verdicts as historical receipts, not current kernel behavior.
• CCC-v2 (corrected envelope handling) supersedes the v1 parser contract where documented.

Loading Examples

from datasets import load_dataset
registry = load_dataset("ariffazil/CCC", "conflict_registry",
                        revision="REPLACE_AFTER_MERGE")   # pin exact commit after merge
archive  = load_dataset("ariffazil/CCC", "historical_probe_archive",
                        revision="REPLACE_AFTER_MERGE")

Relationship to AAA-FFF

Stage: mediated_comparison (series ARIFOS-GOVERNED-INTELLIGENCE-EVALS).

Record-Count Correction — Updated 2026-10-20

Measured live record count: 28 records. The "Current Registry (12 records)" claim
reflected the 2026-09-19 seeding state; the registry has grown since. This is a
documentation correction only — no data files were modified. [OBS — live probe
2026-10-20, 333-AGI session SEAL-95408eb88aef44a1; audit trail: HF card audit
following measured-vs-card drift]