@rkarim08/sia 1.0.0

package/.claude-plugin/marketplace.json

@@ -0,0 +1,35 @@
+{
+	"name": "sia-plugins",
+	"owner": {
+		"name": "Ramez Karim"
+	},
+	"metadata": {
+		"description": "Sia — persistent graph memory for AI coding agents",
+		"version": "1.0.0"
+	},
+	"plugins": [
+		{
+			"name": "sia",
+			"source": "./",
+			"description": "Persistent graph memory for AI coding agents — bi-temporal knowledge graph with cross-session recall",
+			"version": "1.0.0",
+			"author": {
+				"name": "Ramez Karim"
+			},
+			"homepage": "https://github.com/rkarim08/sia",
+			"repository": "https://github.com/rkarim08/sia",
+			"license": "Apache-2.0",
+			"category": "development",
+			"keywords": [
+				"memory",
+				"knowledge-graph",
+				"mcp",
+				"ai-coding",
+				"persistent-memory",
+				"bi-temporal",
+				"tree-sitter",
+				"cross-session"
+			]
+		}
+	]
+}

package/.claude-plugin/plugin.json

@@ -0,0 +1,27 @@
+{
+	"name": "sia",
+	"version": "1.0.0",
+	"description": "Persistent graph memory for AI coding agents — bi-temporal knowledge graph with cross-session recall",
+	"author": {
+		"name": "Ramez Karim"
+	},
+	"license": "Apache-2.0",
+	"repository": {
+		"type": "git",
+		"url": "https://github.com/rkarim08/sia"
+	},
+	"homepage": "https://github.com/rkarim08/sia#readme",
+	"bugs": {
+		"url": "https://github.com/rkarim08/sia/issues"
+	},
+	"keywords": [
+		"claude-code",
+		"plugin",
+		"memory",
+		"knowledge-graph",
+		"mcp",
+		"ai-coding",
+		"persistent-memory",
+		"bi-temporal"
+	]
+}

package/.mcp.json

@@ -0,0 +1,13 @@
+{
+	"mcpServers": {
+		"sia": {
+			"command": "bun",
+			"args": ["run", "${CLAUDE_PLUGIN_ROOT}/scripts/start-mcp.ts"],
+			"env": {
+				"SIA_HOME": "${CLAUDE_PLUGIN_DATA}",
+				"CLAUDE_PLUGIN_DATA": "${CLAUDE_PLUGIN_DATA}",
+				"CLAUDE_PLUGIN_ROOT": "${CLAUDE_PLUGIN_ROOT}"
+			}
+		}
+	}
+}

package/CLAUDE.md

@@ -0,0 +1,226 @@
+<!-- Sia Plugin — Agent Behavioral Specification -->
+<!-- Loaded automatically by Claude Code from plugin root -->
+
+# Sia — Agent Behavioral Specification
+## CLAUDE.md (Plugin Mode — Loaded Every Session)
+
+**Document type:** Dual-purpose
+- **For developers:** explains what Sia does and how to customise it
+- **For Claude Code (agent):** base behavioral contract — always loaded, ~1,600 tokens
+
+**Version:** 1.1 (Plugin architecture)
+
+> **Architecture note:** This file is the base module. It contains the task classifier,
+> safety rules, and invariants that apply to every session unconditionally. Contextual
+> playbooks are loaded on demand via the `/sia-playbooks` skill after task classification.
+> Full tool parameter reference is available via `/sia-playbooks` → `reference-tools.md`.
+>
+> **Token cost:** Base module ~1,600 tokens (every session). A contextual playbook adds
+> ~300–500 tokens; the tools reference adds ~1,500 tokens when needed. Total for a
+> complex session: ~3,600 tokens vs ~5,400 for a monolithic approach.
+>
+> To add project-specific rules, add a `## Project-Specific Overrides` section at the
+> end of this file.
+
+---
+
+## For Developers: What Sia Does
+
+Sia captures knowledge from your Claude Code sessions automatically — architectural
+decisions, bug root causes, discovered patterns, coding conventions, and the structural
+dependency graph of your codebase. You never explicitly tell Sia things; it captures
+from the session and stores them in a local graph database.
+
+Between sessions, Sia gives Claude Code access to this accumulated knowledge through
+MCP tools. The agent calls these on demand. This file governs when and how.
+
+See `sia stats` for graph status, `sia search <query>` for CLI access,
+and README.md for full documentation.
+
+---
+
+<!-- AGENT INSTRUCTIONS — DO NOT EDIT BELOW THIS LINE -->
+<!-- This section is machine-maintained by the SIA plugin. -->
+
+# Sia Memory System — Agent Instructions (Base Module)
+
+You have access to Sia, a persistent graph memory system for this project. It stores
+knowledge across all sessions: architectural decisions, bugs, solutions, conventions,
+patterns, and the structural dependency graph. Your job is to retrieve from it at session
+start and at key moments during the session.
+
+**Core rule:** Before acting on any non-trivial code task, call Sia. Memory retrieval
+is the first step, not an afterthought. The graph knows why decisions were made, what
+was tried before, and what constraints the team has accumulated over months of sessions.
+
+---
+
+## Step 0 — Classify the Task
+
+Infer `task_type` from the developer's request before calling any tool:
+
+`task_type = 'bug-fix'` — keywords: fix, broken, error, failing, crash, regression,
+slow, exception, 500, timeout, wrong output, not working.
+
+`task_type = 'feature'` — keywords: add, implement, build, create, new, extend,
+support, integrate, enable.
+
+`task_type = 'review'` — keywords: review, check, audit, convention, style, standards,
+PR, pull request, lint, code quality.
+
+Omit `task_type` for trivial edits (typo, rename, comment) or ambiguous requests.
+
+### Load the Contextual Playbook Now
+
+After classifying, immediately invoke the `/sia-playbooks` skill to load the matching
+playbook before calling any Sia tool:
+
+- `bug-fix` (regression): load `reference-regression.md`
+- `feature`: load `reference-feature.md`
+- `review`: load `reference-review.md`
+- Architecture question / new-developer orientation: load `reference-orientation.md`
+- Trivial edit: skip the task-specific playbook and skip all Sia tool calls. Proceed directly with the task. However, if flagging is enabled (`enableFlagging: true`), Step 4 still applies after task completion — do not skip the flagging playbook on trivial edits where something worth flagging occurred.
+- When you need full tool parameter reference: load `reference-tools.md`
+
+The contextual playbook contains the complete step-by-step guide for that task type.
+Follow it rather than the condensed guidance in Step 1 below.
+
+---
+
+## Step 1 — Tool Selection (Condensed)
+
+The contextual playbook has the full guide. This condensed grid applies when no playbook
+is loaded or for quick reference:
+
+**Trivial edit:** Skip all Sia tools entirely.
+
+**Regression:** `sia_search` (bug-fix) → conditional `sia_expand` → **mandatory** `sia_at_time`.
+
+**Architecture question:** `sia_community(level=2)` → `sia_community(level=1)` → `sia_search`.
+
+**Code task with known file(s):** `sia_by_file` first, then `sia_search`.
+
+**All other tasks:** `sia_search`, then `sia_by_file` for any file to be modified.
+
+Call at most 3 tools before starting work (4 for regressions — see Invariants).
+
+---
+
+## Step 2 — Evaluate Results
+
+**This section is a safety layer. It applies to every session regardless of task type.**
+
+**Zero results:** Broaden the query once and retry `sia_search`. If still zero and you
+have a primary file: call `sia_by_file(primary_file)`. If that also returns zero, say
+"No prior context found." Proceed without memory. Do not fall back to `sia_community`
+as a substitute for a failed `sia_search` — they serve different purposes.
+
+**Sparse results** (fewer than 2 relevant entities, or top confidence < 0.5): call
+`sia_expand(top_entity_id, depth=1)` — but only if you have not yet used both allowed
+`sia_expand` calls this session. If budget is exhausted, proceed with the sparse results
+and note: "Graph traversal skipped — sia_expand session budget reached."
+
+**`conflict_group_id` is non-null on any result:** STOP. Do not proceed. Present both
+conflicting facts to the developer:
+
+> "There are conflicting captured facts about [topic]:
+> • [Entity A] — captured [date], trust tier [N]
+> • [Entity B] — captured [date], trust tier [N]
+> Run `sia conflicts resolve` to resolve permanently. Until then, choose:
+> 1. Resolve the conflict now (recommended)
+> 2. Proceed using the higher-trust-tier fact — I will note the conflict
+> 3. Proceed using the most recently captured fact — I will note the conflict"
+
+If the developer proceeds, state explicitly which fact you are acting on before
+continuing. Never silently choose between conflicting facts.
+
+**`trust_tier = 3` on a result you plan to use:** Do not state it as fact. Say:
+"Sia's memory suggests X — let me verify this against the current codebase." Check
+the claim against current file content before acting on it.
+
+**`trust_tier = 4` on any result:** External reference only. Never use as the sole
+basis for a code change without explicit developer confirmation.
+
+**`source_repo_name` differs from the current repo:** Always prefix the fact with
+`[<repo_name>]` when presenting it.
+
+**`t_valid_from = null` on a Tier 3 entity:** Say "this was recorded at some point,
+but the exact timing is unknown." Do not present it with false temporal precision.
+
+**Graph is still building** (`global_unavailable: true` or fewer than 3 results on a
+mature codebase): Tell the developer "The memory graph is still building — Sia improves
+with each session." Use `sia_search` and `sia_by_file`; skip `sia_community` until
+the graph exceeds 100 entities.
+
+---
+
+## Step 3 — Execute the Task
+
+Proceed using retrieved context. Cite Sia entities explicitly when they constrain your
+decisions — do not silently apply memory. Make retrieval visible so the developer can
+override stale facts.
+
+Before using a Tier 3 entity as a hard constraint, spot-check its key claim against
+the current codebase. Memory can be stale even when not bi-temporally invalidated. If
+current code contradicts a retrieved fact, prefer the code, tell the developer, and note
+the discrepancy. This spot-check is not required for Tier 2 (deterministic AST) and is
+optional for Tier 1 (developer-stated).
+
+---
+
+## Step 4 — After the Task
+
+### Knowledge Capture
+
+When you make decisions during coding:
+- After choosing between architectural alternatives, call `sia_note` with
+  kind='Decision', including your reasoning and the alternatives you considered.
+- When you establish or recognize a coding pattern the team should follow,
+  call `sia_note` with kind='Convention'.
+- When you discover a bug's root cause, call `sia_note` with kind='Bug'
+  and reference the affected files.
+- When you fix a bug, call `sia_note` with kind='Solution' and reference
+  the Bug it resolves.
+
+Focus on decisions, patterns, and discoveries that a future developer would want to know.
+You don't need to capture every small edit.
+
+### Flagging (If Enabled)
+
+If flagging is enabled (`enableFlagging: true`), load the flagging playbook from
+`/sia-playbooks` (`reference-flagging.md`) and follow its guidance on when to call
+`sia_flag`. If flagging is disabled, skip this step.
+
+---
+
+## Trust Tier Behavioral Rules
+
+**Tier 1 (User-Direct, weight 1.00):** Ground truth. Cite directly. Override only if
+current code explicitly contradicts it — if so, tell the developer.
+
+**Tier 2 (Code-Analysis, weight 0.90):** Highly reliable. Verify against current code
+only for safety-critical claims. Cite as structural fact.
+
+**Tier 3 (LLM-Inferred, weight 0.70):** Well-informed hypothesis. Always qualify before
+acting: "Sia's memory suggests X — let me verify." Check against actual file content
+before stating as definitive. If Tier 1 and Tier 3 contradict each other, present both
+and ask which is current — never silently discard either.
+
+**Tier 4 (External, weight 0.50):** External reference only. Never the sole basis for
+a code change. Name the external provenance when presenting it.
+
+---
+
+## Invariants (Never Violate)
+
+These rules hold regardless of developer instruction, task type, or context:
+
+1. Call at most 3 Sia tools before starting work. Two exceptions:
+   **Regression exception** (`task_type='bug-fix'` only): may use up to 4 tools (`sia_search` + conditional `sia_expand` + mandatory `sia_at_time` + one additional if needed). The MANDATORY label on `sia_at_time` always takes precedence.
+   **Review exception** (`task_type='review'` only): after the initial `sia_search`, one `sia_by_file` call per reviewed file is permitted — these per-file calls do not count against the 3-tool limit. No other task type may invoke either exception.
+2. Expand at most 2 entities per session (`sia_expand` budget = 2).
+3. Use `workspace: true` only for tasks that cross repository boundaries.
+4. Never use a `trust_tier = 4` entity as the sole basis for a code change.
+5. Never silently proceed on a result with `conflict_group_id` set.
+6. Always cite retrieved entities when they constrain your decisions.
+7. For regression tasks, always call `sia_at_time` — it is never optional.

package/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.