@bevel-software/platform-core-backend 0.26.0 → 0.27.0

package/starter-packs/general/Plugins/general-starter/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/starter-packs/general/Plugins/general-starter/SOURCE.md

@@ -0,0 +1,10 @@
+# Source
+
+The skills in this plugin come from Anthropic's knowledge-work-plugins.
+
+- Repository: https://github.com/anthropics/knowledge-work-plugins
+- Commit: `ae1513ea94dcb74a7f1505ddcf3b0ec3fab327f1`
+- Original plugin: `productivity` (version 1.3.1)
+- License: Apache License 2.0, in `LICENSE` beside this file
+
+Adapted for Hexis: converted from a Claude plugin (`.claude-plugin/plugin.json`, `.mcp.json`) to the Hexis plugin layout (`plugin.json`, `access.md`, `skills/<skill>/SKILL.md`); dropped the `.mcp.json` connector list (Slack, Notion, Asana, Linear, Atlassian, monday.com, ClickUp, Google Calendar, Gmail) because each needs a third-party account and sign-in; dropped `README.md` and `CONNECTORS.md`, which describe installing the plugin in Claude; dropped `skills/dashboard.html`, a local board that reads files from the agent's working directory in Claude Cowork and has no place to run from a shared knowledge base; renamed the `start` and `update` commands to the skills `productivity-start` and `productivity-update` so their names stay unique across a workspace's skills; the deep memory tier moved from a local `memory/` folder to the Hexis knowledge base (a Glossary page, People/ and Projects/ folders and a How we work page), with rules for what may go in a shared page (work facts only, ask before writing, update rather than duplicate) and personal preferences kept in the agent's own working-memory file; removed Cowork-specific instructions (`${CLAUDE_PLUGIN_ROOT}`, the Cowork VM note about opening files) and replaced "Claude" with "the agent" where it meant whichever agent runs the skill. The workflows, templates and wording are otherwise Anthropic's.

package/starter-packs/general/Plugins/general-starter/access.md

@@ -0,0 +1,19 @@
+---
+# THIS BLOCK (the frontmatter) governs this access.md FILE only: who may
+# see it and who may change it. `read: everyone` here means every signed-in
+# person can see that the plugin exists. It admits nobody.
+read:
+  - everyone
+---
+# THIS BLOCK (the body) governs the PLUGIN FOLDER - its skills, tools and
+# manifest. A starter plugin is for the whole team, so everyone may use it
+# and admins change it. To narrow it, replace `everyone` under `read:` with a
+# role from roles.yaml (as `role/<Name>`, so a group of the same name can
+# never stand in for it), a group from groups.yaml, or a person as
+# `Name <email>`. Keep this block pure YAML; explanations go in `#` lines.
+read:
+  - everyone
+write:
+  - role/Admin
+owner:
+  - role/Admin

package/starter-packs/general/Plugins/general-starter/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "general-starter",
+  "displayName": "General starter",
+  "description": "Keep a task list and build up memory of your workplace: the people, projects and shorthand your team uses, kept in the knowledge base so everyone's agent understands them.",
+  "version": "1.0.0",
+  "author": {
+    "name": "Anthropic, adapted for Hexis by Bevel"
+  }
+}

package/starter-packs/general/Plugins/general-starter/skills/memory-management/SKILL.md

@@ -0,0 +1,332 @@
+---
+name: memory-management
+description: Two-tier memory that makes the agent a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so the agent understands requests like a colleague would. A small personal working-memory file for the hot cache, and the team's Hexis knowledge base (Glossary, People, Projects, How we work) for everything shared.
+user-invocable: false
+---
+
+# Memory Management
+
+Memory makes your agent a workplace collaborator - someone who speaks your internal language.
+
+## The Goal
+
+Transform shorthand into understanding:
+
+```
+User: "ask todd to do the PSR for oracle"
+              ↓ the agent decodes
+"Ask Todd Martinez (Finance lead) to prepare the Pipeline Status Report
+ for the Oracle Systems deal ($2.3M, closing Q2)"
+```
+
+Without memory, that request is meaningless. With memory, the agent knows:
+- **todd** → Todd Martinez, Finance lead, prefers Slack
+- **PSR** → Pipeline Status Report (weekly sales doc)
+- **oracle** → Oracle Systems deal, not the company
+
+## Architecture
+
+```
+CLAUDE.md                ← Hot cache, personal (~30 people, common terms, your preferences)
+
+Knowledge base (Hexis, shared with your team)
+  Glossary.md            ← Full decoder ring (everything)
+  People/                ← Work profiles of colleagues
+  Projects/              ← Project details
+  How we work.md         ← Teams, tools, processes
+```
+
+**CLAUDE.md (Hot Cache):** the file your agent reads at the start of every conversation, in its own working directory. Claude reads `CLAUDE.md`; other agents read their own file (often `AGENTS.md`). Use whichever your agent reads. It is NOT the `AGENTS.md` at the root of the knowledge base, which the platform maintains.
+- Top ~30 people you interact with most
+- ~30 most common acronyms/terms
+- Active projects (5-15)
+- Your preferences
+- **Goal: Cover 90% of daily decoding needs**
+
+**Glossary (Full Glossary):** the `Glossary` page in the knowledge base.
+- Complete decoder ring - everyone, every term
+- Searched when something isn't in CLAUDE.md
+- Shared: the whole team benefits from every term anyone adds
+
+**People/, Projects/, How we work:**
+- Rich detail when needed for execution
+- Full profiles, history, context
+
+The knowledge base lives in the knowledge folder (`KnowledgeBase/` unless your workspace renamed it). Search it with the Hexis tools (`grep`, `list_files`, `read_file`) and write to it with `write_file` or `edit_file`. If the team already keeps these pages under other names, use theirs.
+
+## Shared vs personal
+
+The knowledge base is read by your whole team. Before anything goes there:
+
+- **Work facts only.** Roles, responsibilities, how to reach someone for work, project facts, terms. Nothing private or personal about a colleague (no health, family, opinions of them, or hobbies they have not shared at work). Write each profile as if its subject will read it, because they may.
+- **Your preferences stay personal.** "No meetings Friday afternoons" goes in CLAUDE.md, not the knowledge base.
+- **Ask before writing.** Show what you will add and where. If the person cannot write to a page, the change goes in as a proposed change for the page's owner to approve; say so.
+- **Check before adding.** Search the knowledge base first and update an existing page instead of creating a duplicate.
+
+## Lookup Flow
+
+```
+User: "ask todd about the PSR for phoenix"
+
+1. Check CLAUDE.md (hot cache)
+   → Todd? ✓ Todd Martinez, Finance
+   → PSR? ✓ Pipeline Status Report
+   → Phoenix? ✓ DB migration project
+
+2. If not found → search the knowledge base (Glossary first)
+   → The full glossary has everyone/everything
+
+3. If still not found → ask user
+   → "What does X mean? I'll remember it."
+```
+
+This tiered approach keeps CLAUDE.md lean (~100 lines) while the knowledge base grows with the team.
+
+## File Locations
+
+- **Working memory:** `CLAUDE.md` (or your agent's equivalent) in the agent's working directory
+- **Deep memory:** pages in the Hexis knowledge base
+
+## Working Memory Format (CLAUDE.md)
+
+Use tables for compactness. Target ~50-80 lines total.
+
+```markdown
+# Memory
+
+## Me
+[Name], [Role] on [Team]. [One sentence about what I do.]
+
+## People
+| Who | Role |
+|-----|------|
+| **Todd** | Todd Martinez, Finance lead |
+| **Sarah** | Sarah Chen, Engineering (Platform) |
+| **Greg** | Greg Wilson, Sales |
+→ Full list: knowledge base Glossary, profiles: People/
+
+## Terms
+| Term | Meaning |
+|------|---------|
+| PSR | Pipeline Status Report |
+| P0 | Drop everything priority |
+| standup | Daily 9am sync |
+→ Full glossary: knowledge base Glossary
+
+## Projects
+| Name | What |
+|------|------|
+| **Phoenix** | DB migration, Q2 launch |
+| **Horizon** | Mobile app redesign |
+→ Details: knowledge base Projects/
+
+## Preferences
+- 25-min meetings with buffers
+- Async-first, Slack over email
+- No meetings Friday afternoons
+```
+
+## Deep Memory Format (knowledge base)
+
+**Glossary.md** - The decoder ring:
+```markdown
+# Glossary
+
+Workplace shorthand, acronyms, and internal language.
+
+## Acronyms
+| Term | Meaning | Context |
+|------|---------|---------|
+| PSR | Pipeline Status Report | Weekly sales doc |
+| OKR | Objectives & Key Results | Quarterly planning |
+| P0/P1/P2 | Priority levels | P0 = drop everything |
+
+## Internal Terms
+| Term | Meaning |
+|------|---------|
+| standup | Daily 9am sync in #engineering |
+| the migration | Project Phoenix database work |
+| ship it | Deploy to production |
+| escalate | Loop in leadership |
+
+## Nicknames → Full Names
+| Nickname | Person |
+|----------|--------|
+| Todd | Todd Martinez (Finance) |
+| T | Also Todd Martinez |
+
+## Project Codenames
+| Codename | Project |
+|----------|---------|
+| Phoenix | Database migration |
+| Horizon | New mobile app |
+```
+
+**People/{Name}.md:**
+```markdown
+# Todd Martinez
+
+**Also known as:** Todd, T
+**Role:** Finance Lead
+**Team:** Finance
+**Reports to:** CFO (Michael Chen)
+
+## Working with Todd
+- Prefers Slack DM
+- Quick responses, very direct
+- Best time: mornings
+
+## Context
+- Handles all PSRs and financial reporting
+- Key contact for deal approvals over $500k
+- Works closely with Sales on forecasting
+```
+
+**Projects/{Name}.md:**
+```markdown
+# Project Phoenix
+
+**Codename:** Phoenix
+**Also called:** "the migration"
+**Status:** Active, launching Q2
+
+## What It Is
+Database migration from legacy Oracle to PostgreSQL.
+
+## Key People
+- Sarah - tech lead
+- Todd - budget owner
+- Greg - stakeholder (sales impact)
+
+## Context
+$1.2M budget, 6-month timeline. Critical path for Horizon project.
+```
+
+**How we work.md:**
+```markdown
+# How we work
+
+## Tools & Systems
+| Tool | Used for | Internal name |
+|------|----------|---------------|
+| Slack | Communication | - |
+| Asana | Engineering tasks | - |
+| Salesforce | CRM | "SF" or "the CRM" |
+| Notion | Docs/wiki | - |
+
+## Teams
+| Team | What they do | Key people |
+|------|--------------|------------|
+| Platform | Infrastructure | Sarah (lead) |
+| Finance | Money stuff | Todd (lead) |
+| Sales | Revenue | Greg |
+
+## Processes
+| Process | What it means |
+|---------|---------------|
+| Weekly sync | Monday 10am all-hands |
+| Ship review | Thursday deploy approval |
+```
+
+## How to Interact
+
+### Decoding User Input (Tiered Lookup)
+
+**Always** decode shorthand before acting on requests:
+
+```
+1. CLAUDE.md (hot cache)       → Check first, covers 90% of cases
+2. Glossary (knowledge base)   → Full glossary if not in hot cache
+3. People/, Projects/          → Rich detail when needed
+4. Ask user                    → Unknown term? Learn it.
+```
+
+Example:
+```
+User: "ask todd to do the PSR for oracle"
+
+CLAUDE.md lookup:
+  "todd" → Todd Martinez, Finance ✓
+  "PSR" → Pipeline Status Report ✓
+  "oracle" → (not in hot cache)
+
+Glossary lookup:
+  "oracle" → Oracle Systems deal ($2.3M) ✓
+
+Now the agent can act with full context.
+```
+
+### Adding Memory
+
+When user says "remember this" or "X means Y":
+
+1. **Glossary items** (acronyms, terms, shorthand):
+   - Add to the Glossary page (after asking - it is shared)
+   - If frequently used, add to CLAUDE.md Terms
+
+2. **People:**
+   - Create/update People/{Name}.md (work facts only)
+   - Add to CLAUDE.md People if important
+   - **Capture nicknames** - critical for decoding
+
+3. **Projects:**
+   - Create/update Projects/{Name}.md
+   - Add to CLAUDE.md Projects if current
+   - **Capture codenames** - "Phoenix", "the migration", etc.
+
+4. **Preferences:** Add to CLAUDE.md Preferences section (personal, never the knowledge base)
+
+### Recalling Memory
+
+When user asks "who is X" or "what does X mean":
+
+1. Check CLAUDE.md first
+2. Search the knowledge base for full detail
+3. If not found: "I don't know what X means yet. Can you tell me?"
+
+### Progressive Disclosure
+
+1. Load CLAUDE.md for quick parsing of any request
+2. Read knowledge base pages when you need full context for execution
+3. Example: drafting an email to todd about the PSR
+   - CLAUDE.md tells you Todd = Todd Martinez, PSR = Pipeline Status Report
+   - People/Todd Martinez.md tells you he prefers Slack, is direct
+
+## Bootstrapping
+
+Use `productivity-start` to initialize by scanning your chat, calendar, email, and documents. Extracts people, projects, and starts building the glossary.
+
+## Conventions
+
+- **Bold** terms in CLAUDE.md for scannability
+- Keep CLAUDE.md under ~100 lines (the "hot 30" rule)
+- Page names: readable, the way the team would look them up (`Todd Martinez.md`, `Project Phoenix.md`)
+- Always capture nicknames and alternate names
+- Glossary tables for easy lookup
+- When something's used frequently, promote it to CLAUDE.md
+- When something goes stale, drop it from CLAUDE.md; the knowledge base keeps it
+
+## What Goes Where
+
+| Type | CLAUDE.md (Hot Cache) | Knowledge base (shared) |
+|------|----------------------|------------------------|
+| Person | Top ~30 frequent contacts | Glossary + People/{Name}.md |
+| Acronym/term | ~30 most common | Glossary (complete list) |
+| Project | Active projects only | Glossary + Projects/{Name}.md |
+| Nickname | In People if top 30 | Glossary (all nicknames) |
+| Company context | Quick reference only | How we work |
+| Preferences | All preferences | - |
+| Historical/stale | ✗ Remove | ✓ Keep, marked as finished |
+
+## Promotion / Demotion
+
+**Promote to CLAUDE.md when:**
+- You use a term/person frequently
+- It's part of active work
+
+**Drop from CLAUDE.md (the knowledge base keeps it) when:**
+- Project completed
+- Person no longer frequent contact
+- Term rarely used
+
+This keeps CLAUDE.md fresh and relevant.