Vertical seed packs marketplace

Topic

From the PointSav Documentation

PointSav intends to distribute curated industry-specific seed packs as starter taxonomies, enabling tenants to contribute refinements back through a planned marketplace.

Updated 2026-05-01 · HistoryEspañol

The Vertical Seed Packs Marketplace is a planned distribution mechanism for industry-specific starter taxonomies that provision the knowledge graph of a new customer tenant. Each pack bundles Archetypes, a Chart of Accounts, Domains, Themes, a glossary, and MCP server extensions suited to a particular business vertical. Customers may install packs at provisioning, update them as new versions are released, and are intended to be able to contribute refinements back to the marketplace for other operators in the same vertical. See the seed-taxonomy SMB bootstrap.

[edit]Pack content

Each pack is a curated bundle in open formats:

  • Archetypes JSON file — industry-specific role identities
  • Chart of Accounts JSON file — industry-specific business profiles
  • Domains JSON file — macro work categories
  • Themes JSON file — starter time-bound initiatives (typically sparse; the customer adds their own)
  • Glossary CSV — terms in common use in the vertical
  • MCP server extensions configuration — vertical-specific tools (for example, a point-of-sale integration for a restaurant or an electronic health record integration for a hospital)
  • Pack manifest — metadata, version, license, and contributors

[edit]Reference packs

PointSav intends to develop and maintain a set of reference packs at Phase 5 launch. The planned set includes a pack for small and mid-size restaurants, one for law firms of thirty to three hundred lawyers, one for small and rural hospitals, one for mid-size property development firms, and a universal default pack for businesses that do not fit a specific vertical.

The Woodfine real estate pack is the current reference implementation, derived from the Woodfine deployment's existing seed taxonomy and validated in production operation.

[edit]How packs are intended to be distributed

The planned distribution mechanism routes through the marketplace gateway. Operators are intended to browse available packs within the TUI, install a pack with a single command, and receive a diff preview before applying future pack updates. The install process imports the pack's JSON files into the per-tenant knowledge graph in `service-content` and immediately enables content classification. The operator then customizes the installed taxonomy for their specific business.

[edit]Customer contribution

When a customer extends their pack with additions useful to others in the same vertical, they may be able to contribute the additions back. The intended flow guides the operator through review, sanitization, and consent before creating a marketplace contribution. Accepted contributions are intended to land in the next pack version, benefiting other tenants in the vertical without requiring PointSav to author all pack content.

This contribution mechanism is the structural opening for community-driven vertical evolution. Its governance model — how contributions are reviewed and accepted — is a pending operator decision that will be determined during Phase 5 implementation.

[edit]Pack licensing

Reference packs are intended to ship under a permissive license. Customer-contributed additions would retain customer copyright but grant distribution rights for marketplace inclusion.

The customer-owned-graph-ip principle applies at the instance level, not the pack level: the customer's running knowledge graph (their customized instance of a pack) is their intellectual property; the pack itself is permissively licensed material that the customer customized from.

[edit]Composition

Vertical Seed Packs are the distribution mechanism for the seed-taxonomy-as-smb-bootstrap pattern — they carry the canonical form of the four-part taxonomy for a specific industry. The planned reverse-flow-substrate marketplace is intended to include packs as first-class inventory alongside data listings and adapter weights.

[edit]See also

Edit this page · View source