reclaim/app/lib/data/repository.dart
flemming-it 8ee6a294a1 feat: initial F∆I Law-Heatmap Phase 0 scaffold
First end-to-end-buildable cut of the pflicht-/graph-basierte
Wirkungsanalyse von Rechtsnormen, running on Ch∆In. Demo runs
without external dependencies and without a hub connection so
the methodology + UI stack can be reviewed before any Verbands-
Kooperation or Beirats-Validierung kicks in.

Tree layout

  MACHBARKEITSSTUDIE.md       v0.3 — pflicht-basierte Methodik,
                              4-Tier-Evidenz, 8 law*-Module
                              auf Ch∆In statt der alten F∆I-
                              Plattform.
  RUN.md                      one-page how-to-run.
  flows/durchstich-gewo-14.yaml
                              vertical Phase-0 flow: pull →
                              normalize → duties → citations →
                              cohort → skm → frust → benefit →
                              attribution → system.approval.
  app/                        Flutter macOS client, design
                              language pulled from fai_web
                              (ink #08090A, paper #F4F3EF,
                              petrol signal #2E8F9E). Mock
                              repository ships five fixture
                              norms with real source URLs and a
                              permanent T4 demo-banner so no
                              figure can be mistaken for a
                              validated one.

Module repos (separate, see chain-modules*/):

  text-akoma-normalize, text-deontic-extract, graph-citation-
  extract, text-readability-score, stats-cohort-size, graph-
  shapley-attribution, econ-skm-score, law-benefit-score.

What runs today

  - flutter analyze: 0 issues
  - flutter test: 2/2 (landing + nav-to-shell smoke)
  - flutter build macos (via app/build-macos.sh) and ad-hoc
    codesign, app launches and the Dart VM service comes up
  - native cargo test green on every module
  - cargo build --release --target wasm32-wasip2 produces a
    130 KiB artefact for text-akoma-normalize

What is deliberately mock / stub

  - gRPC wire from the client to a chain serve hub (Repository
    abstraction is in place; live impl is the next step)
  - NKR Bürokratiekosten-Datenbank ingestion (for the canonical
    h-Werte that close out the Engpass per Studie §6.7)
  - DESTATIS GENESIS-API adapter for stats.cohort_size

License: Apache-2.0. Author/contact in MACHBARKEITSSTUDIE.md.
Signed-off-by: flemming-it <sf@flemming.it>
2026-06-18 11:26:28 +02:00

38 lines
1 KiB
Dart

import 'models.dart';
import 'fixtures.dart';
/// Repository abstraction for evaluations.
///
/// Phase 0 ships exactly one implementation: [MockRepository],
/// backed by [Fixtures]. The live implementation (gRPC against a
/// running `chain serve`) lands in Phase 0 week 1 — its API will
/// match this interface so no UI change is needed.
abstract class EvaluationRepository {
Future<List<Evaluation>> list();
Future<Evaluation?> byEli(String eli);
String get mode;
String get hubLabel;
}
/// In-memory, no-network implementation. Marks itself clearly so
/// the UI shows a "demo mode" badge.
class MockRepository implements EvaluationRepository {
const MockRepository();
@override
Future<List<Evaluation>> list() async => Fixtures.evaluations;
@override
Future<Evaluation?> byEli(String eli) async {
for (final e in Fixtures.evaluations) {
if (e.norm.eli == eli) return e;
}
return null;
}
@override
String get mode => 'demo';
@override
String get hubLabel => 'in-memory fixtures (kein Hub)';
}