sophiagraph 0.0.1__tar.gz

sophiagraph-0.0.1/API_COMPATIBILITY.md

@@ -0,0 +1,119 @@
+# sophiagraph API Compatibility Policy
+
+Owner: `sophiagraph`
+Status: `active`
+Scope: stable import-root and versioning policy for external `sophiagraph` consumers
+
+## Purpose
+
+Define what external consumers can rely on when they build against the
+standalone `sophiagraph` package.
+
+## Stable import roots
+
+External consumers should treat these import roots as the supported public API:
+
+- `sophiagraph`
+- `sophiagraph.models`
+- `sophiagraph.query`
+- `sophiagraph.storage`
+- `sophiagraph.portability`
+- `sophiagraph.adapters`
+- `sophiagraph.canvas`
+- `sophiagraph.extensions`
+- `sophiagraph.views`
+- `sophiagraph.audit`
+- `sophiagraph.trust`
+- `sophiagraph.temporal`
+- `sophiagraph.contracts`
+
+The top-level `sophiagraph` package is the preferred entrypoint for common usage.
+
+## Stable top-level exports
+
+The following top-level exports are part of the current public contract:
+
+- `sophiagraph.__version__`
+- `sophiagraph.DEFAULT_DB_FILENAME`
+- `sophiagraph.SophiaGraphSqliteStore`
+- `sophiagraph.SophiaGraphMemoryStore`
+- `sophiagraph.MemoryNamespace`
+- `sophiagraph.MemoryNamespaceComponent`
+- `sophiagraph.MemoryRecord`
+- `sophiagraph.MemoryCandidate`
+- `sophiagraph.MemoryRelation`
+- `sophiagraph.KnowledgeDocument`
+- `sophiagraph.KnowledgeDocumentBlock`
+- `sophiagraph.StructuralLink`
+- `sophiagraph.ExplicitLinkResolver`
+- `sophiagraph.LinkResolution`
+- `sophiagraph.LinkResolutionCandidate`
+- `sophiagraph.ListQueryOptions`
+- `sophiagraph.SearchQueryOptions`
+- `sophiagraph.LinkQueryOptions`
+- `sophiagraph.LocalGraphOptions`
+- `sophiagraph.GraphSnapshotOptions`
+- `sophiagraph.GraphSnapshot`
+- `sophiagraph.StructuralSearchQuery`
+- `sophiagraph.create_sqlite_store(...)`
+- `sophiagraph.create_memory_store()`
+- `sophiagraph.default_db_path(...)`
+- `sophiagraph.audit`
+- `sophiagraph.contracts`
+- `sophiagraph.portability`
+- `sophiagraph.trust`
+- `sophiagraph.coerce_temporal_dt`
+
+## Versioning posture
+
+`sophiagraph` is currently `0.x` software.
+
+That means:
+
+1. additive API changes are preferred,
+2. breaking changes are still possible,
+3. breaking changes must be called out in release notes and package docs,
+4. stable import roots should not be moved casually even during `0.x`.
+
+## Deprecation policy
+
+When a public symbol or import path needs to change:
+
+1. prefer an additive replacement first,
+2. document the new path in `README.md`,
+3. keep the old path available for at least one `0.x` release when practical,
+4. remove only after the deprecation is documented in release notes.
+
+If a safety or correctness issue requires immediate removal, the release notes
+must say so explicitly.
+
+## Compatibility tests
+
+Public-contract confidence should be enforced by tests that cover:
+
+1. import-root availability,
+2. public top-level export availability,
+3. store-behavior regressions for package-owned backends,
+4. portability round-trip expectations,
+5. namespace-safe query/export/import boundaries,
+6. explicit link/backlink/local-graph behavior across memory and SQLite stores,
+7. Markdown/frontmatter structural import behavior with no prose rewrites,
+8. release/install smoke for built artifacts.
+
+## Internal compatibility shims
+
+Underscore-prefixed model cast helpers and codec hydrator aliases may remain
+available during `0.x` for OpenMinion compatibility, but they are not part of
+`__all__` and should not be used by new external consumers. New code should use
+public model imports and public codec helpers such as `record_from_dict`.
+
+## Non-goals
+
+This policy does not promise:
+
+1. host-framework orchestration semantics,
+2. an Obsidian editor, renderer, sync service, or plugin runtime,
+3. semantic inference of tags, links, relation types, or summaries from prose,
+4. compatibility for private helper modules,
+5. long-term support for undocumented import paths,
+6. compatibility with every possible third-party graph backend.

sophiagraph-0.0.1/LICENSE

@@ -0,0 +1,201 @@
+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.

sophiagraph-0.0.1/MANIFEST.in

@@ -0,0 +1,8 @@
+include LICENSE
+recursive-include scripts *.py
+recursive-include examples *.py
+include API_COMPATIBILITY.md
+include README.md
+include RELEASING.md
+recursive-exclude * __pycache__ *.py[cod]
+prune src/*.egg-info

sophiagraph-0.0.1/PKG-INFO

@@ -0,0 +1,340 @@
+Metadata-Version: 2.4
+Name: sophiagraph
+Version: 0.0.1
+Summary: Standalone wisdom graph substrate for durable agent memory
+Author: Sophiagraph Contributors
+License-Expression: Apache-2.0
+Keywords: agent,wisdom,knowledge-graph,memory,sqlite,durable-memory
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Topic :: Database
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: build<2,>=1; extra == "dev"
+Requires-Dist: pytest<9,>=8; extra == "dev"
+Requires-Dist: ruff<1,>=0.11; extra == "dev"
+Requires-Dist: twine<7,>=5; extra == "dev"
+Dynamic: license-file
+
+# sophiagraph
+
+Status: `publish-ready alpha`
+Shape: standalone Python package
+License: `Apache-2.0`
+
+`sophiagraph` is a standalone wisdom graph substrate for durable agent memory.
+The name comes from Greek `Sophia` (`Σοφία`), meaning wisdom; in this package it
+frames durable knowledge as a graph of records, relations, provenance, trust,
+and portable snapshots.
+
+## What the package provides
+
+`sophiagraph` currently provides:
+
+- canonical durable-memory models
+- contract and provenance helpers
+- query DTOs
+- portability bundle models and codec helpers
+- audit-event schemas
+- trust and temporal primitives
+- typed namespace DTOs for explicit tenant/user/agent/session isolation
+- directed relation APIs with explicit incoming/outgoing/bidirectional lookup
+- Obsidian-style structural document/link DTOs, Markdown/frontmatter adapter,
+  backlinks, outgoing links, local graph traversal, graph snapshots, structural
+  search DTOs, saved view DTOs, JSON Canvas DTOs, and extension hooks
+- a package-local SQLite durable engine
+- a package-local in-memory backend for tests and ephemeral consumers
+- a standalone smoke entrypoint for publish/install validation
+
+## What the package does not provide
+
+This package does **not** provide:
+
+- application orchestration or gateway policy
+- a full Obsidian clone, editor, sync service, or visual renderer
+- provider/model routing
+- session orchestration
+- automatic link, tag, relation, entity, or summary inference from prose
+- implicit imports back into any host framework
+
+Host frameworks remain the orchestrators. `sophiagraph` owns reusable durable
+wisdom graph primitives and the standalone durable engine.
+
+## Install
+
+Editable install during local development:
+
+```bash
+python3.11 -m pip install -e .
+```
+
+Wheel build:
+
+```bash
+python3.11 -m build
+```
+
+Fresh-wheel smoke:
+
+```bash
+TMP_VENV="$(mktemp -d)/sophiagraph-venv"
+python3.11 -m venv "$TMP_VENV"
+"$TMP_VENV/bin/pip" install dist/sophiagraph-*.whl
+"$TMP_VENV/bin/sophiagraph-smoke" --root /tmp/sophiagraph-release-smoke --seed --json
+```
+
+## Standalone Smoke
+
+Source-root smoke:
+
+```bash
+PYTHONPATH=src python3.11 -m sophiagraph --root /tmp/sophiagraph-smoke --seed --json
+```
+
+Installed-console-script smoke:
+
+```bash
+sophiagraph-smoke --root /tmp/sophiagraph-smoke --seed --json
+```
+
+## External Consumer Quickstart
+
+Minimal standalone flow for another framework or service:
+
+```python
+from sophiagraph.models import MemoryNamespace, MemoryRecord
+from sophiagraph.portability.models import MemoryBundleExportOptions, MemoryBundleImportOptions
+from sophiagraph.query import ListQueryOptions, SearchQueryOptions
+from sophiagraph.storage import create_memory_store, create_sqlite_store
+
+store = create_sqlite_store("/tmp/sophiagraph-demo")
+namespace = MemoryNamespace(
+    tenant_id="tenant-demo",
+    user_id="user-demo",
+    agent_id="demo",
+    graph_id="main",
+)
+store.put_record(
+    MemoryRecord(
+        id="rec-1",
+        scope="agent:demo",
+        type="fact",
+        key="project:apollo",
+        title="Apollo launch date",
+        content={"text": "Apollo launched in Q2"},
+        created_at="2026-05-22T00:00:00+00:00",
+        updated_at="2026-05-22T00:00:00+00:00",
+        source="validated",
+        confidence=0.95,
+        event_time="2026-05-22T00:00:00+00:00",
+        namespace=namespace,
+    )
+)
+
+namespace_filter = MemoryNamespace(agent_id="demo")
+records = store.list_records(
+    ListQueryOptions(scopes=["agent:demo"], namespaces=[namespace_filter])
+)
+search_hits = store.search_records(
+    SearchQueryOptions(query="Apollo", scopes=["agent:demo"], namespaces=[namespace_filter])
+)
+snapshot = store.export_snapshot(
+    MemoryBundleExportOptions(scopes=["agent:demo"], namespaces=[namespace_filter])
+)
+import_store = create_memory_store()
+import_store.import_snapshot(snapshot, MemoryBundleImportOptions())
+```
+
+Runnable example:
+
+```bash
+PYTHONPATH=src python3.11 examples/basic_usage.py
+PYTHONPATH=src python3.11 examples/obsidian_substrate.py
+```
+
+## Typed Namespaces
+
+Records still accept the legacy `scope` string for compatibility. New
+integrations can also attach typed namespace DTOs to records and use the same
+typed dimensions for query/export/import boundaries:
+
+```python
+from sophiagraph.models import MemoryNamespace
+
+namespace = MemoryNamespace(
+    tenant_id="tenant-acme",
+    user_id="user-j",
+    agent_id="agent-codex",
+    session_id="session-123",
+    graph_id="main",
+)
+
+legacy_scope = namespace.to_scope("agent")
+
+record = MemoryRecord(
+    id="rec-namespace",
+    scope=legacy_scope,
+    type="fact",
+    content={"text": "Namespace-safe records keep tenant and agent separate."},
+    created_at="2026-05-23T00:00:00+00:00",
+    updated_at="2026-05-23T00:00:00+00:00",
+    namespace=namespace,
+)
+
+records = store.list_records(
+    ListQueryOptions(scopes=[legacy_scope], namespaces=[MemoryNamespace(agent_id="agent-codex")])
+)
+```
+
+Namespace values must be explicit caller-provided identifiers. `sophiagraph`
+does not infer tenant, user, project, or agent identity from prose. Existing
+SQLite rows without namespace columns are migrated from their explicit legacy
+`scope` value only; no content or title text is inspected.
+
+## Graph Relations
+
+Relations are explicit, typed, directed edges between records. Consumers can
+list outgoing, incoming, or bidirectional edges through the `direction` option:
+
+```python
+outgoing = store.list_relations("rec-1")
+incoming = store.list_relations("rec-1", direction="in")
+neighborhood = store.get_related_records(
+    "rec-1",
+    ["agent:demo"],
+    direction="both",
+)
+```
+
+The package does not infer relation types from prose. Callers must submit
+relation records directly.
+
+## Obsidian-Style Knowledge Graph Substrate
+
+`sophiagraph` now has package-core surfaces for Obsidian-comparable structural
+workflows:
+
+- `KnowledgeDocument` wraps document-profile `MemoryRecord` nodes with path,
+  title, aliases, content hash, namespace, timestamps, and provenance.
+- `StructuralLink` represents explicit wikilinks, Markdown links, embeds,
+  property links, external URLs, unresolved targets, headings, and block refs.
+- `extract_markdown(...)` parses frontmatter, aliases, tags, and explicit link
+  syntax without modifying note prose.
+- Store backends expose `put_link(...)`, `list_links(...)`,
+  `get_backlinks(...)`, `get_outgoing_links(...)`, `get_local_graph(...)`, and
+  `get_graph_snapshot(...)`.
+- Structural search, saved views, JSON Canvas, and extension hooks are durable
+  DTO/helper surfaces. They do not require a UI renderer or OpenMinion import.
+
+Example:
+
+```python
+from sophiagraph.adapters.markdown import extract_markdown
+from sophiagraph.models import LinkResolutionCandidate, MemoryNamespace
+from sophiagraph.query import LinkQueryOptions, LocalGraphOptions
+
+namespace = MemoryNamespace(agent_id="demo", graph_id="main")
+imported = extract_markdown(
+    "See [[Roadmap]].",
+    path="Index.md",
+    record_id="rec-index",
+    namespace=namespace,
+    resolver_candidates=[
+        LinkResolutionCandidate(
+            record_id="rec-roadmap",
+            path="Roadmap.md",
+            title="Roadmap",
+            namespace=namespace,
+        )
+    ],
+)
+for link in imported.links:
+    store.put_link(link)
+
+backlinks = store.list_links(LinkQueryOptions(record_id="rec-roadmap", direction="in"))
+local_graph = store.get_local_graph(LocalGraphOptions(record_id="rec-index", depth=1))
+```
+
+The resolver contract is deliberately structural: explicit path first, then
+case-insensitive title/alias matching inside the namespace. Unresolved and
+ambiguous targets are preserved as first-class outcomes. Unlinked mentions are
+not persisted as graph edges.
+
+## Alpha-Scale Search and SQLite Connections
+
+Current search is deterministic substring search over hydrated record payloads.
+It is suitable for alpha-scale package use and tests, but it is not yet an
+FTS5-backed or vector-backed retrieval engine. The hybrid retrieval roadmap owns
+the future FTS/vector/rerank design.
+
+`SophiaGraphSqliteStore` opens a short-lived SQLite connection per method call.
+That keeps alpha behavior simple and avoids hidden shared connection state. A
+pooled or long-lived connection strategy should be introduced only with a
+separate lifecycle/concurrency contract.
+
+## Cross-Package Compatibility DTOs
+
+Some contract DTOs, including runtime snapshot/capsule/query shapes and
+`MemoryPatchResult`, are retained for host-runtime adapters such as OpenMinion
+and future service surfaces. They are compatibility contracts; package-local
+stores are not required to instantiate every DTO.
+
+## Import Boundary Rule
+
+`sophiagraph` must never import from host frameworks such as OpenMinion.
+
+Dependency direction is one-way:
+
+- allowed: host framework -> `sophiagraph`
+- forbidden: `sophiagraph` -> host framework
+
+## Public API
+
+Stable top-level exports for external consumers:
+
+- `sophiagraph.SophiaGraphSqliteStore`
+- `sophiagraph.SophiaGraphMemoryStore`
+- `sophiagraph.create_sqlite_store(...)`
+- `sophiagraph.create_memory_store()`
+- `sophiagraph.default_db_path(...)`
+- `sophiagraph.audit`
+- `sophiagraph.contracts`
+- `sophiagraph.portability`
+- `sophiagraph.trust`
+- `sophiagraph.coerce_temporal_dt`
+
+Supported import roots:
+
+- `sophiagraph`
+- `sophiagraph.models`
+- `sophiagraph.query`
+- `sophiagraph.storage`
+- `sophiagraph.portability`
+- `sophiagraph.adapters`
+- `sophiagraph.canvas`
+- `sophiagraph.extensions`
+- `sophiagraph.views`
+- `sophiagraph.audit`
+- `sophiagraph.trust`
+- `sophiagraph.temporal`
+- `sophiagraph.contracts`
+
+## API Compatibility
+
+Compatibility and deprecation policy:
+
+- `API_COMPATIBILITY.md`
+
+## Release Docs
+
+Package-local release runbook:
+
+- `RELEASING.md`
+- `scripts/release_check.py`