Skip to content

[META] Epic index #71

Description

@a-a-k

Epic Index

This issue tracks all top-level epics:

Release Status

Synced on 2026-05-31 after shipping v0.2.4, validating release assets, refreshing release/package tracking, and recording the Bering v0.3.4 app/package sync.

  • Latest public release: v0.2.4 technical preview
  • Historical shipped milestones: v0.1.0 technical preview, v0.1.1 technical preview, v0.2.0 technical preview, v0.2.1 technical preview, v0.2.2 technical preview, v0.2.3 technical preview, v0.2.4 technical preview
  • Active backlog milestone: Post-v0.2.4 technical preview
  • Previous release-tracking issue: #82
  • Current release-tracking issue: #83
  • Current upstream Bering app/package sync target: Bering v0.3.4, recorded in MB3R-Lab/Sheaft@64ea26a
  • Repository-side roadmap: docs/roadmap.md

Release/package checkpoint

The published v0.2.4 release payload is the baseline for the next cycle:

  • Release URL: https://github.com/MB3R-Lab/Sheaft/releases/tag/v0.2.4
  • Release manifest asset: release-manifest.json (sha256:e358eb1a06f22e6880f9bb7fc51031fec6d42c2f950abb2fb66249dc6f35bfea)
  • Default config pack asset: sheaft-default-config-pack_0.2.4.tar.gz (sha256:2c2b7854c1f7310fcc3488b72c82514aebf8bbbe66b217d5a29e394b4757f4d0)
  • Helm chart package asset: sheaft-0.2.4.tgz (sha256:983a47c68df3ce4c7914dc98426c0d43f8af27ffee40d4b420dbb1162ce990f4)
  • Benchmark quality report asset: quality-report.json (sha256:f27c866c38dfae3b28a121944ace47ee6abfdaca965569fcb6bf227dcb0ea14b)
  • OCI image: ghcr.io/mb3r-lab/sheaft:v0.2.4 (sha256:a434b5fb3f034a58455b20fa27a6976aa79d66340814f4cd81549b20bd8a5db8)
  • OCI chart: oci://ghcr.io/mb3r-lab/charts/sheaft:0.2.4 (sha256:f12887b3a34eede2b3426c0aeea3313b8978c324620475be74ad670f4f24b0a1)

Upstream Bering sync checkpoint

The current Sheaft main line is app-level synced against Bering v0.3.4 while keeping the same accepted Bering schema contract pins.

  • Bering release/package: https://github.com/MB3R-Lab/Bering/releases/tag/v0.3.4
  • Bering release manifest asset: release-manifest.json (sha256:d7f4b3d61ff8e36bd370dadd351e51a2b2803677ae12a5e0fbb81faacfd01e20)
  • Bering contracts pack asset: bering-contracts_0.3.4.tar.gz (sha256:3865a8e7152c8a383f34d99334bc392cfd0ec793325b530d392723f67839ddbf)
  • Sheaft sync commit: 64ea26a1bb33cba77fea0b6fcdf07cb883d072a3
  • compatibility-manifest.json records tested_bering_app_versions: ["v0.3.4"]
  • Accepted schema contract pins remain io.mb3r.bering.model@1.0.0, io.mb3r.bering.snapshot@1.0.0, io.mb3r.bering.model@1.1.0, and io.mb3r.bering.snapshot@1.1.0
  • Sync CI passed: ci-template-smoke run 26717682013, schema-contract run 26717682015, and release-dry-run run 26717682014

Completed Trustability And Explainability Steps

  • R4.1 Public benchmark suite for Sheaft-on-Bering is closed. make benchmark-slice runs the fixed public slice from benchmarks/fixed-slice/manifest.json.
  • R4.2 Quality metrics for Sheaft-on-Bering is closed. The slice emits quality-report.json with repeatability and quality checks.
  • R4.3 Negative results and applicability boundaries / do-not-trust signals is closed. docs/assumptions-and-limitations.md publishes detector IDs, manual heuristics, severity, remediation, and the future report field shape.
  • R9.1 Why mode for Bering-based gate decisions is closed. Reports include policy_evaluation.reasons; summary.md includes Why; sheaft gate/run --why prints decision causes.

Current Priority Backlog

  1. R9.2 Debugging toolkit for contract and path analysis
  2. R9.3 Dependency-level explanations for posture diffs and serve mode
  3. R3.4 Scalability on large Bering snapshots
  4. R5.3 Chaos triage from Bering-driven risk outputs
  5. R1.3 Remaining resiliency interpretation gaps (fallback/rate-limit)
  6. R7.3 Pilot-to-production playbook (Bering -> Sheaft)

Product Capability Ordering

The next roadmap emphasis remains explainability and operator actionability before broadening the analysis surface. Pluginization remains useful, but it should follow debugging, dependency-level explanation, and benchmark scale work that make current gate decisions defensible.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: docsDocumentation and examplespriority: p0Highest priority for MVPtype: epicEpic-level scope

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions