feat: deliver buyer evidence board and source-grounded ontology surface - #258
Open
seonghobae wants to merge 386 commits into
Open
feat: deliver buyer evidence board and source-grounded ontology surface#258seonghobae wants to merge 386 commits into
seonghobae wants to merge 386 commits into
Conversation
Opening Public post from Demo Corp members now names the first Keyman after landed evaluation. Home list opens do not add that copy.
…210) Opening Public post from Demo Corp members now lands Ada West related nodes under the first-Keyman next action, ahead of Affiliate tree. Home list opens still wait for a Keyman click.
Opening Public post from Demo Corp members now names the first related node after landed Ada West related. Home list opens do not add that copy.
Opening Public post from Demo Corp members now lands Priya Nair related nodes under the first-related next action, ahead of Affiliate tree. Home list opens still wait for a related click.
…223) Opening Public post from Demo Corp members now focuses the Ask heading after Priya Nair related nodes are current. Home list opens do not steal that focus.
Opening Public post from Demo Corp members now lands Ask about this lineage under the Ask next action, ahead of Affiliate tree. Home list opens keep Ask after Keyman.
Opening Public post from Demo Corp members now names the first seeded Ask after landed chat. Home list opens do not add that copy.
Classify organization similarity outcomes as unique, miss, or tie. Keep ties unbound before Keyman name rewriting and after the creation-lock reload so live resolution and inference cannot insert a third AUTO catalog row. Base branch only: feat/role-responsibility-agent-ontology. #74 remains open and unmerged to main.
…6.0) (#231) Opening Public post from Demo Corp members now lands the first seeded Ask answer under the Ask seed next action, ahead of the input. Home list opens keep that answer after the input.
Opening Public post from Demo Corp members now names Linked post as the first cited source after the landed first Ask answer. Home list opens do not add that copy.
Request stays disabled until GET /api/me returns affiliated corps so a multi-affiliation operator cannot POST before the picker appears. POST /api/analysis-runs records Pending lineage only. TEPP and period-report kinds 422 before any snapshot write. Do not invent a theta. Co-authored-by: Cursor Agent <[email protected]> Co-authored-by: Seongho Bae <[email protected]>
Store cataloged_person_id on post_summary_role so a person chip walks the stored catalog row even when Keyman was not extracted on that post. Lookup orders by created_at, then person_id. Historical backfill leaves two same-named mentions unbound (ADR 0027). Co-authored-by: Cursor Agent <[email protected]> Co-authored-by: Seongho Bae <[email protected]>
…ion (v2.8.0) (#237) Opening Public post from Demo Corp members now lands the first cited evidence under the citation next action, ahead of the input. Home list opens still wait for a citation click.
Opening Public post from Demo Corp members now names Event Lineage after Linked post evidence is current. Home list opens do not add that copy.
…lineage' into feat/analysis-run-name-evidence-lineage
Record current protected main as an explicit parent after #74 was squash-merged independently. Preserve the newer Buyer/Global Ask/runtime tree on this branch, while keeping release metadata monotonic at 2.12.6. Exact-head CI and review evidence must be regenerated on this merge candidate.
…lineage' into feat/analysis-run-name-evidence-lineage
This was referenced Aug 19, 2026
… guidance Live gap (2026-08-19): two reported symptoms on real image content -- (1) OCR on a table-shaped image flattened its text into an unstructured list (the same row-grouping loss chunk_by_dom had for real HTML tables, now fixed there too), and (2) locate_regions's 'distinct meaningful visual regions' framing let the model describe only the most visually striking part of an image and skip the rest, instead of covering the whole DOM/image area. The OCR prompt now asks for one row per line with ' | ' between columns when the image contains a table (the parser already preserves multi-line TEXT, verified via a new table-shaped-response test). The region prompt now explicitly requires full edge-to-edge image coverage, not just the most striking parts.
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
2 participants
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.
Summary
This PR carries the protected-branch-safe Buyer product path from the semantic-lineage development tree into
main.Current-main reconciliation
PR #74 was squash-merged into protected
mainindependently while the semantic-lineage branch continued to advance. The Buyer branch was reconciled without force-pushing by recording protectedmain@690f35285717af52c2033960efb8b0177c3b6a88as ancestry while preserving the later Buyer/runtime tree.Current exact head:
2012101cb9e2b7fdbd821cb65708915ddf7bd88e.Release metadata is monotonic at v2.12.6, immediately before stacked #260 v2.13.0. GitHub currently reports the PR mergeable against protected main.
Security hardening at current head
The browser/API OIDC verifier is fail-closed:
kidis mandatory; no first-key fallback exists.KEYVERSE_AUDIENCEorOIDC_AUDIENCE; resource audience is not inferred from the browser OAuth client id.lineageweave-apiin access-tokenaud.This matches the OAuth JWT access-token resource-audience model in RFC 9068;
CHANGELOG.d/2.12.6-oidc-resource-audience.mdrecords the contract.Revalidated stale-parent failures
The old #260 merge-ref Python failure came from an obsolete #258 snapshot. Current #258 already contains the parent-level fixes for ADR README hygiene, source-state/context/search migrations in fixtures, non-transactional
CREATE INDEX CONCURRENTLYmigration replay, and embedding/static-analysis cleanup. These fixes must not be reimplemented in children.Validation gate
Remembered pre-reconciliation evidence is stale. Exact-head Tests, Security Scan, SAST Semgrep, and PROV-O contract for
2012101cb9e2b7fdbd821cb65708915ddf7bd88eare authoritative. Do not merge while any required run is queued/pending/failed/skipped-required.All current review threads are resolved. After current-head checks reach terminal success, re-fetch formal reviews and require the live protected-branch independent approval policy. Do not self-approve or force-merge.
Stack
#258 → #260 → #261 → #262 → #263 → #264 → draft #265#260 must be semantically restacked onto the repaired #258 head rather than carrying its stale parent snapshot. #264 has a valid analysis-run cutoff-navigation finding; its one-shot RED→GREEN repair is already present on the branch and must complete before that PR advances.