Jorijn van der Graaf
339f4b9b40
Beside the push gates, crafter-review runs the pre-send review of a kernel contributor's workbench: --mode series over a format-patch export with its cover letter, --mode reply over a mail draft. The inventory partitions a cover letter, a plain mail and the camera review's shape; ten kernel lenses join the table with their gates (structure, code, artifact truth) and the persona gate - one maintainer-persona instance per --reviewers entry, its whole pass gating its blocks and pruning the units that are not theirs. A series' code units are keyed on the code like the push gates'; every text unit on its text, the references it cites and the anchor when it is dated. The references an artifact cites are prefetched through utilities/lore.py into the gate-state, with a digest in the run layer, and a persona's calibration map is its lore listing. The kernel schema carries the persona vocabulary, the kernel note kinds, the predicted review and the not-mine list; the matrix the persona holes, the thin and the modelled units; gates clean without a persona pass is GATES CLEAN. A reply's gate-state sits beside the draft and is read once; a kernel mode needs --subsystem, defaults the effort to max and the trees to work/linux,work/milos-linux, and excuses no unit from the holes. The kernel lenses and the common text ship verbatim; the table lists them after the push gates' lenses and the config template holds them off, so a repository that never turns them on changes nothing. Prompts, keys and plans were checked byte for byte against the pipeline these modes replace, on its own artifacts: two replies and a series, every system prompt, user prompt, job and reuse key identical.
25 lines
1.4 KiB
C++
25 lines
1.4 KiB
C++
// SPDX-License-Identifier: AGPL-3.0-only
|
|
// SPDX-FileCopyrightText: Copyright (C) 2026 Catcrafts®
|
|
|
|
export module Crafter.Review:Dispositions;
|
|
import std;
|
|
import :Json;
|
|
|
|
// The disposition register: which entries are in force (a hash match),
|
|
// carried (every anchor text still occurs its recorded number of times) or
|
|
// lapsed, and the DISPOSITIONS IN FORCE prompt block. Entries are the
|
|
// owner's JSON, kept as it is.
|
|
export namespace Crafter::Review::Dispositions {
|
|
// The register's entries with an id; empty `path`: none.
|
|
std::vector<Json> Load(std::string_view path);
|
|
// [{id, status, detail}], statuses in-force | carried | lapsed. The
|
|
// series and commits modes carry by anchor count; a reply never carries.
|
|
std::vector<Json> Classify(std::span<const Json> entries, std::string_view hash, const std::filesystem::path& artifact, std::string_view mode = "commits");
|
|
// The entries the rows say are in force or carried.
|
|
std::vector<Json> InForce(std::span<const Json> entries, std::span<const Json> rows);
|
|
// The DISPOSITIONS IN FORCE block for one lens: a kernel lens gets the
|
|
// kernel pipeline's rules (the ledger, captures, lore), a persona its
|
|
// disposition-review duty; a subsystem names the ledger whose waiver rows
|
|
// lapse when not listed.
|
|
std::string Block(std::span<const Json> inForce, std::span<const Json> rows, std::string_view lensFile, std::string_view hash, std::string_view subsystem = {});
|
|
}
|