{"ecosystem":"commerce","generated":"2026-10-26","events":[{"date":"2026-10-26","kind":"moved","entity":"capability","ref":"capability:agent-guidance","name":"Agent guidance","what":"coverage by ecosystem, coverage by flavor revised","detail":"Reassessed against the graph (check:capabilities): docs/WRITING.md §3 rules out provider counts and absence claims in every capability field."},{"date":"2026-10-17","kind":"moved","entity":"capability","ref":"capability:agent-systems-access","name":"Agent access to your systems","what":"description revised","detail":"Keep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit."},{"date":"2026-10-16","kind":"entered","entity":"person","ref":"actor:abinayaaa","name":"Abinaya Srinivasan"},{"date":"2026-10-15","kind":"moved","entity":"capability","ref":"capability:agent-guidance","name":"Agent guidance","what":"coverage by ecosystem, framing by ecosystem, facets, coverage by flavor, framing by flavor revised","detail":"[skillOverflow](artifact:dankromp-skilloverflow) entered on 2026-09-18, after this flavor was assessed, serves the UI5 door and states no flavor, so by the flavor rule it answers in all of them. Its own skill list names SAPUI5 data binding, custom controls, i18n and testing and nothing about the component library, so it is reported as a fallback rather than read as a community presence here. Saying so is what keeps core-only honest beside the options the page lists."},{"date":"2026-10-12","kind":"entered","entity":"person","ref":"actor:andreescocard","name":"André Escocard"},{"date":"2026-10-12","kind":"entered","entity":"person","ref":"actor:emenowicz","name":"Dawid Michałowicz"},{"date":"2026-10-12","kind":"moved","entity":"capability","ref":"capability:agent-systems-access","name":"Agent access to your systems","what":"core coverage, coverage by ecosystem, description revised","detail":"Maintainer requested complementary boundaries so a CAP bridge can connect system access and application MCP exposure, while implementation restrictions remain explicit. Domains, providers and task classifications are unchanged."},{"date":"2026-10-09","kind":"entered","entity":"option","ref":"artifact:andreescocard-hybris-mcp-lite","name":"hybris-mcp-lite","discovered_via":"source:curator · handed over for the SAP Commerce door after ADR-0033 reopened the 2026-10-09 decline"},{"date":"2026-10-09","kind":"entered","entity":"option","ref":"artifact:abinayaaa-sap-cx-developer-companion","name":"sap-cx-developer-companion","discovered_via":"source:sap-ai-skills-library · skills.cloud.sap"},{"date":"2026-10-09","kind":"moved","entity":"capability","ref":"capability:agent-systems-access","name":"Agent access to your systems","what":"entry revised","detail":"Split out of MCP servers at the maintainer's decision. That capability named a protocol and carried two concerns: exposing what you built to agents, which stays there under a name that says so, and giving agents a way into an SAP system you run, which is this one. Thirty providers moved with their own sentences; the Commerce and SuccessFactors slots moved with them. Named beside agent access to your code, its development-time sibling."},{"date":"2026-10-09","kind":"moved","entity":"capability","ref":"capability:agent-guidance","name":"Agent guidance","what":"ecosystems revised","detail":"SAP Commerce opened as a product door (docs/concepts/product-doors.md, ADR-0033) and [sap-commerce-skill](artifact:emenowicz-sap-commerce-skill) entered behind it with no tile to sit under. Packaged knowledge for the Commerce type system, service layer, ImpEx and OCC API is the same concern the node already holds on four doors, so the key was added rather than the capability forked."},{"date":"2026-10-09","kind":"moved","entity":"option","ref":"artifact:andreescocard-hybris-mcp-lite","name":"hybris-mcp-lite","what":"entry, provides revised","detail":"The concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.","drafted_with_ai":true},{"date":"2026-10-09","kind":"moved","entity":"option","ref":"artifact:emenowicz-sap-commerce-skill","name":"sap-commerce-skill","what":"entry revised","detail":"Declined on scope on 2026-09-10, with no Commerce door and no Commerce capability for it to attach to, and reopened in data/curation/decisions.json once the product door opened (docs/concepts/product-doors.md, ADR-0033). Written from the repository's own README; hard rule 7: skills are indexed, never authored here.","drafted_with_ai":true},{"date":"2026-10-09","kind":"moved","entity":"option","ref":"artifact:abinayaaa-sap-cx-developer-companion","name":"sap-cx-developer-companion","what":"entry revised","detail":"A new repository in the SAP AI Skills Library registry snapshot of 2026-10-09, registering one skill at skills/sap-cx-developer-companion. Written from the repository's own README and SKILL.md; hard rule 7: skills are indexed, never authored here. Placed behind the SAP Commerce door because the CX API explorer and the error resolver are written against Commerce Cloud OCC and Sales and Service Cloud, with CAP and BTP as served doors for the CDS half.","drafted_with_ai":true},{"date":"2026-09-14","kind":"moved","entity":"capability","ref":"capability:agent-guidance","name":"Agent guidance","what":"coverage by flavor, framing by flavor revised","detail":"The door-level framing already says the Web Components skills ship inside the library and version with it; a flavor paragraph names the two skills the flavor's provider actually carries rather than repeating the door's sentence."},{"date":"2026-09-10","kind":"entered","entity":"option","ref":"artifact:emenowicz-sap-commerce-skill","name":"sap-commerce-skill","discovered_via":"source:curator · handed over for the SAP Commerce door after ADR-0033 reopened the 2026-09-10 decline"},{"date":"2026-09-10","kind":"moved","entity":"capability","ref":"capability:agent-guidance","name":"Agent guidance","what":"ecosystems revised","detail":"Artifacts that answer this concern sat behind the ABAP door with no tile to appear under, so browse counted them and rendered nothing. The concern is one a ABAP developer actually decides there, which is the test for opening a door rather than trimming a serves claim."},{"date":"2026-09-09","kind":"moved","entity":"capability","ref":"capability:agent-guidance","name":"Agent guidance","what":"description, ecosystems revised","detail":"The cross-ecosystem sentence said \"writes correct CAP\", which was true when CAP was the only door. The CAP-specific wording moved into framing_by_ecosystem.cap where it belongs, and the node's own description now describes the concern rather than one ecosystem's version of it."},{"date":"2026-09-07","kind":"moved","entity":"capability","ref":"capability:agent-guidance","name":"Agent guidance","what":"core coverage, gap revised","detail":"The gap's premise was that no SAP-published skill existed. One does now, so the gap is no longer about absence — it is about how much of the corpus four skills reach."}]}