Repository navigation
feat(amico-run): meeting + paper triage — the two dormant intakes (#1686) - #1697
Merged
Merged
Conversation
…rain flywheel slice 7, #1686) The two dormant intakes, wired into the claim layer: - amico extract-meetings: given a pending-tag meeting note, propose its three tag tiers (the meeting vault's OWN registry is the canon — closed tier-1 vocabularies, tier-2 entities minted only from the note's own attendee canonicals + partnership phrases, tier-3 themes free-form), a context-links section with resolvable links (transcript sibling, series sessions, this pass's hopper proposals), and next-steps → hopper proposals carrying resolvable meeting-note provenance. Where the closed vocabulary has no fit the proposal names the gap — never invented. - amico triage-papers: a relevance-high paper yields a claim-shaped hypothesis-seed proposal (frontmatter EXACTLY the claim object, a paper/ evidence pointer) against the problem cards whose platform identity matches the paper's systems — exact, no fuzzy bridging; no match → no seed, named honestly. - both: dry-run by default, idempotent on re-run (deterministic naming + bytes), the notturno pass receipt on the distill chassis gates (deny-list, job membership, record-mode self-filter), and the meeting vault / papers intake are read-only substrates — proposals land in a --out the caller names. - claims lint: the paper/ + meeting-note/ evidence-pointer kinds resolve (POINTER_KINDS + the lint's substrates extend the #1681 vocabulary). TDD: fixture notes per intake + idempotency assertions + live smoke green against one real pending-tag meeting note and one real high-relevance paper; claims/distill/lifecycle suites unchanged-green.
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #1679. Closes #1686. TDD green: 56 new tests (triage 31 + both verbs), regression surfaces unchanged-green, typecheck clean. extract-meetings: canon-closed tag proposals from the vault's OWN registry, context links (transcript + series siblings), next-steps → hopper with meeting-note provenance; 3 canon gaps NAMED not papered (recurring-external type missing, no canon product match, internal-projects.md/aliases.md absent from the registry). triage-papers: relevance-high → claim-shaped hypothesis seed, platform-identity match against problem cards, validateClaim-green. Both dry-run default, idempotent (md5-verified byte-stable re-runs on real data), receipts on the distill chassis. Live demos on a real pending-tag note + a real high paper; the ro mounts never written.