Capture: ten31-database Matrix-bridge intake for fundraising grid

2026-06-16 14:14:25 -05:00
parent 123072f8ad
commit e2fc522096
1 changed files with 1 additions and 0 deletions
@@ -42,3 +42,4 @@ Example:
 - [ ] (recap-relay) [chore][P3] AGENTS.md endpoint list mis-describes POST /relay/analyze as "{ transcript, … } → topic sections JSON". The actual route (server/routes/analyze.js) takes a free-form { prompt: string } and returns the standard envelope { result: { text } }; "topic sections JSON" is only what the recap-app caller asks for in its prompt. Fix the request-shape wording to { prompt } — surfaced resolving Recaps' Daily Digest synthesis contract (Q4), 2026-06-15
 - [ ] (ten31-database) [bug][P2] Service package icon on StartOS is oversized/zoomed in and needs a better rendering — research Start9 icon spec, source or provide base ten31 logo, and produce a correctly sized icon before the next s9pk upload, 2026-06-16
 - [ ] (keysat) [chore][P2] Design-contract cleanup from the 2026-06-16 design-checker audit — full detail in keysat ROADMAP "Design (contract conformance)" + design/DESIGN.md. (1) Fix 3 blockers (code violates the contract's named "never" rules on live CTAs): (a) gold-as-fill on admin `.featured-pill-toggle.on` (licensing-service-startos/licensing-service/web/index.html:418) → navy fill or gold border+text; (b) gold-as-fill on admin `#tier-banner-cta` upgrade button (web/index.html:537-542) → navy primary; (c) primary buy CTA pill radius 999px (keysat-xyz-landing/index.html:384-385) → r-md 8px. (2) Structural: consolidate the 4 surfaces' inlined CSS-variable copies onto canonical design/brand/palette.css (import it, drop private copies). (3) Token gaps (tokenize-vs-snap): 14px landing card radius; wordmark letter-spacing 0.30 vs 0.28em (add letterSpacing.wordmark token); semantic badge text one-offs (#205c47/#7a5814/#8a2828); hardcoded syntax-highlight hex → var(); admin #f6f1e7 off-token. Re-run design-checker after to confirm, 2026-06-16
+- [ ] (ten31-database) [feature][P2] Matrix-bridge intake for the fundraising grid — use the matrix-bridge repo's pattern to listen on a dedicated ten31-database Matrix room; send a message (with optional business card photo) and a local LLM via Spark Control parses it into the fundraising grid schema, auto-creates the investor entity + contact row; for existing investors, send a meeting note and it appends an interaction log entry; approval gate: the bot replies in Matrix with the proposed add/edit, user approves/rejects/edits in-thread before the write commits, 2026-06-16