pylon-customer-historylisted

# pylon-customer-history Pylon is the inbox where customers' bugs and feature asks land. Turning each thread into a structured memory — tied to the customer's **pylon-account** surface entity — gives the vault the third leg of the customer triad (contact relationship + recent meeting + open commitment). ## Goal When asked "what's going wrong with [[Acme]]?" the kit should answer via entity-mediated retrieval on `[[Acme Pylon]]` (the surface entity) — not keyword search. That requires every Pylon-derived memory to link structurally back to the customer's pylon-account surface. ## Read (before saving) 1. **Does the customer have a pylon-account surface entity?** ``` entity_resolve "<Customer Name> Pylon" ``` If not, create it under `entities/surfaces/pylon-<customer-slug>.md`: ```yaml --- id: "entity:surface:pylon-<slug>" name: "<Customer> Pylon" type: surface surface_kind: pylon-account medium: pylon about: ["[[<Customer>]]"] participants: ["[[<CS owner>]]"] # if known parent: "entity:<your-org-slug>" # from .mvkit/org.json, or null --- ``` 2. **Check existing Pylon memories for this customer:** ``` memory_search entities=["[[<Customer> Pylon]]"] ``` Dedupe on `source_ref:` (Pylon thread URL). 3. **Check active coverage gaps tied to this customer:** ``` memory_search type=feedback tags=coverage-gap entities=["[[<Customer>]]"] ``` A G14 "triad missing" gap is what Pylon ingest is here to fill. ##