Skip to content
Satyam Pariyar

Compiled Practice

Change the evidence. The compiled view keeps its scope, provenance, freshness, and uncertainty visible.

This model uses local examples. It does not inspect a real repository, run commands, or fetch hosted controls.

Choose a scenario

Guidance, package metadata, and CI agree. Hosted protection remains separately unknown.

Want to test the authority rule yourself? Start with two sources that agree, then change one field.

Native evidence

root: /acme/service

freshness limit: 30 days

  • ENGINEERING.mdEngineering guidance

    Supports: Changes are tested in CI

    available · observed 0 days ago · inside scope · precedence 3

  • package.jsonPackage manifest

    Supports: Changes are tested in CI

    available · observed 0 days ago · inside scope · precedence 2

  • .github/workflows/ci.ymlCI workflow

    Supports: Changes are tested in CI

    available · observed 0 days ago · inside scope · precedence 2

  • github:branch-protectionHosted control

    Supports: Branch protection is enabled

    unavailable · observed 0 days ago · inside scope · precedence 1

Compiled findings

Select a finding to trace it back to the evidence that supports it.

The strongest current evidence supports the practice.

scope: /acme/service

Provenance

ENGINEERING.md, package.json, .github/workflows/ci.yml

Limit: Structural evidence does not prove runtime behavior.

The relevant source is understood, but it was unavailable to inspect.

scope: /acme/service

Provenance

github:branch-protection

Limit: The source is understood but was not available to inspect.

Distinct outcomes, never one score

  • pass
  • fail
  • unknown
  • stale
  • unsupported
  • conflicting