INDEPENDENT POLICY & RESEARCHConceptual framework Edition 0.17.0
CORE-014 · Method 0.2.0

Declared Authority and Consent Gate

Which proposed activities remain stopped, unresolved, or restricted to a fictional exercise?

Operational calculation / structured check · Unit tested · Not empirically calibrated

Load MAR-HTP example · MAR-HTP support and governance examples

Worked example

A public agency can document which human approvals apply to a proposed civilian activity and when they expire. Qualified reviewers decide whether the cited authority applies.

Checks explicit authority declarations and required human signoffs for declared activity types.

Try it yourself

The calculator opens with the fictional example already filled in. Change one input, choose Calculate locally, and compare the result to the original values below. Use Reset fictional fixture to start over.

An unknown result means the available inputs do not support a value. Check the calculator’s Warnings tab for what is missing or uncertain.

Go to the calculator Browse all calculators

Changing the label does not improve capacity, speed, error rates or confidence. Enter measured differences explicitly.
Comparison conditions and human review
Record budget, staffing, resources, information release dates, scenario conditions and evaluation criteria. Material differences can make options not comparable.

This declaration is not legal certification. Blocked, pending or assumed gates stop transaction-dependent evaluation.

Keep units consistent within each table. Enter zero when the amount is known to be zero. Leave optional amounts blank when they are unknown. If a required value is missing, the calculator will ask for it.

Advanced: complete input envelope and optional fields

Edit optional fields using the method dictionary. Apply validates and recalculates the entire input. Unknown values remain null.

Import local JSON or CSV

Files stay in this browser. Maximum 1 MiB. JSON imports are recalculated. CSV supports flat observation tables, with column types taken from the displayed fixture. Empty cells become null.

Compare the arrangements

Keep physical resources and evaluation conditions equal. With identical inputs, all three approaches produce identical arithmetic. The comparison refuses material differences in declared conditions; it does not verify those declarations.

Privacy: comparison inputs may contain sensitive notes or operational details. Storage is off by default. Do not enter personal records or sensitive infrastructure details. Reproduction exports include supplied inputs and notes, including raw small-cell inputs suppressed from CORE-009 result tables. Suppression of displayed results does not make a reproduction export safe to publish.

Executive brief and reproducible export

Review for personal, confidential or sensitive material before saving or sharing. No automatic submission occurs.

Read the generated brief

Method, inputs and limits

Checks explicit authority declarations and required human signoffs for declared activity types. Method version 0.2.0. Cannot interpret law, infer permission from a country or commodity, or certify legal clearance.

CORE-014 input dictionary
InputUnit / typeRequired interpretation
authorityReview — Proposed action, actor, jurisdiction, legal citation, approval, restrictions and legal reviewrecord / jsonApproved status requires a named or pseudonymous authorized human reviewer, a cited reference and a review date. Include asOf to evaluate dated declarations at that instant.
activities — Activities and activity typesrecords / jsonEach activity needs a unique ID, label, and explicit type.
declarations — Authority declarations and signoffsrecords / jsonDeclare blocked, unresolved, assumed, or approved; include affected types, required roles, signoffs, reason and reference. Use optional affectedActivityIds to narrow scope and effectiveFrom/validUntil for the supplied effective window.

Visible mathematics / decision rules

Applicable declarations match the activity type and any declared activity IDs. Dated declarations use effectiveFrom inclusive and validUntil exclusive.

The supplied-record gate passes when an applicable approval is effective, required signoffs are approved, and no applicable block, unresolved declaration, or exercise assumption remains.

What this result cannot establish

What would falsify the assumptions?

Reproducible fictional fixture and independently calculated expectations

This fixture is synthetic. It does not describe a country, government, company or event.

{
  "observations": {
    "unit": "declarations",
    "origin": "synthetic",
    "sources": [
      {
        "id": "SYN-001",
        "kind": "synthetic",
        "label": "Fictional example",
        "url": null
      }
    ],
    "authorityReview": {
      "proposedAction": "Fictional civilian transfer and independent local record review",
      "actor": "Fictional civilian service office",
      "jurisdiction": "Fictional jurisdiction; no real legal permission implied",
      "citedLegalAuthority": "SYN-001 fictional exercise authority",
      "approvalStatus": "approved",
      "restrictions": [
        "No real transaction is authorized by this fixture"
      ],
      "lastLegalReview": "2027-01-01",
      "reviewer": {
        "identityOrPlaceholder": "Fictional reviewer A",
        "role": "Designated authority reviewer",
        "authorizedHuman": true
      }
    },
    "activities": [
      {
        "id": "TRANSFER",
        "label": "Fictional civilian transfer",
        "type": "transaction-dependent"
      },
      {
        "id": "LOCAL",
        "label": "Read independent local record",
        "type": "local-independent"
      }
    ],
    "declarations": [
      {
        "id": "D1",
        "status": "blocked",
        "affectedActivityTypes": [
          "transaction-dependent"
        ],
        "requiredSignoffs": [
          "authority reviewer"
        ],
        "signoffs": [],
        "reason": "Consent withdrawn in this fictional exercise",
        "reference": "SYN-001"
      },
      {
        "id": "D2",
        "status": "approved",
        "affectedActivityTypes": [
          "local-independent"
        ],
        "requiredSignoffs": [
          "record owner"
        ],
        "signoffs": [
          {
            "role": "record owner",
            "status": "approved",
            "reference": "SYN-001"
          }
        ],
        "reason": "Local record access explicitly approved in the fixture",
        "reference": "SYN-001"
      }
    ]
  },
  "parameters": {}
}

Expected checks

{
  "stopped": 1,
  "unresolved": 0,
  "exerciseOnly": 0,
  "declaredApproved": 1,
  "transactionEligible": 0
}
Download input fixture

Authoritative background references

These sources inform definitions or review practices. They do not validate this implementation or endorse MAR.

Document decision authority and review