graphfakos 0.0.1__tar.gz

graphfakos-0.0.1/API_COMPATIBILITY.md

@@ -0,0 +1,36 @@
+# GraphFakos API Compatibility
+
+GraphFakos is a `0.0.1` semantic-alpha package. Public APIs are intentionally
+small and centered on provider-neutral graph viewing.
+
+## Stable Import Roots
+
+- `graphfakos`
+- `graphfakos.adapters`
+- `graphfakos.contracts`
+- `graphfakos.models`
+- `graphfakos.provider`
+- `graphfakos.render`
+- `graphfakos.server`
+- `graphfakos.static`
+- `graphfakos.testing`
+- `graphfakos.ui`
+
+## Compatibility Promise
+
+GraphFakos keeps the following surfaces stable within the `0.0.x` line unless a
+release note says otherwise:
+
+- DTO class names
+- provider protocol method names
+- provider-neutral `diagnose_graph()` output shape
+- `screen_manifest()` keys for `screen`, `label`, `route`, and `summary`
+- console script names
+- local preview server helper names
+- screen manifest helper names
+- testing assertion helper names
+- PEP 561 type marker presence through `graphfakos/py.typed`
+
+Provider-specific semantics are not part of GraphFakos core compatibility.
+Sophiagraph, PragmaGraph, OpenMinion, and third-party providers own their own
+semantic compatibility promises.

graphfakos-0.0.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,45 @@
+# Code of Conduct
+
+## Our standard
+
+We are committed to a respectful, constructive, and inclusive community.
+
+Examples of expected behavior:
+
+1. Be respectful and professional.
+2. Assume good intent and discuss ideas, not people.
+3. Give and receive feedback constructively.
+4. Help keep discussions focused and collaborative.
+
+Examples of unacceptable behavior:
+
+1. Harassment, discrimination, or personal attacks.
+2. Threatening, abusive, or hateful language.
+3. Doxxing or sharing private information without consent.
+4. Deliberate disruption, trolling, or bad-faith engagement.
+
+## Scope
+
+This Code of Conduct applies in project spaces (issues, PRs, discussions, chat,
+and reviews).
+
+## Enforcement
+
+Maintainers are responsible for enforcing this Code of Conduct and may remove,
+edit, or reject content or contributions that violate it.
+
+Possible actions include:
+
+1. Warning
+2. Temporary restriction
+3. Permanent ban from project spaces
+
+## Reporting
+
+Report concerns to maintainers through the project's private contact method or
+by asking maintainers for a private channel.
+
+## Attribution
+
+This policy is inspired by common open source community standards and adapted
+for this project.

graphfakos-0.0.1/CODE_QUALITY.md

@@ -0,0 +1,93 @@
+# GraphFakos Code Quality and Hygiene
+
+This is the public contributor version of the package's code-quality rules.
+
+The short version:
+
+1. keep provider-neutral contracts typed and explicit,
+2. keep package boundaries honest,
+3. keep runtime behavior structural rather than speculative,
+4. keep comments minimal,
+5. and prove the change with validation.
+
+## 1. Prefer One Truthful Owner
+
+Use the nearest clear owner:
+
+1. DTOs in `models.py`,
+2. provider protocol and validation in `provider.py`,
+3. rendering entrypoints in `render.py`, `static.py`, and `ui/`,
+4. local preview serving in `server.py`,
+5. reusable test assertions in `testing/`,
+6. fixture/demo providers in `adapters/`.
+
+Avoid duplicate viewer shells, repeated magic literals, and wrappers that only
+rename another helper.
+
+## 2. Keep Runtime Behavior Structural
+
+GraphFakos owns graph display and interaction. It does not decide whether a
+memory, source item, claim, citation, or provider payload is true.
+
+Prefer:
+
+1. typed fields,
+2. explicit provider capabilities,
+3. deterministic static export,
+4. clear adapter boundaries.
+
+Avoid:
+
+1. hidden Sophiagraph or PragmaGraph assumptions,
+2. hidden OpenMinion runtime imports,
+3. lossy fact extraction or semantic inference in the viewer package.
+
+## 3. Keep Names and Layout Honest
+
+Rules:
+
+1. remove stale names instead of letting them linger,
+2. keep files in the package area that truthfully owns them,
+3. do not grow generic junk-drawer files like `utils.py`,
+4. keep provider-specific mapping in provider packages or fixture adapters.
+
+## 4. Keep Public Docs Portable
+
+Do not add:
+
+1. machine-local absolute paths,
+2. private workstation assumptions,
+3. internal tracker-state wording as public package documentation.
+
+## 5. Keep Changes Focused
+
+Good practice:
+
+1. one clear purpose per PR,
+2. update tests near the change,
+3. avoid unrelated refactors in the same patch.
+
+## 6. Validate Before Calling Work Done
+
+Before closing work, run the package gates from `graphfakos/`:
+
+```bash
+make check
+```
+
+If your change affects packaging or public release shape, also run:
+
+```bash
+make release-check
+```
+
+Use `make lint` or `make test` directly only when you need a narrower loop
+while iterating.
+
+## 7. When in Doubt, Choose Clarity
+
+The package prefers:
+
+1. explicit owners over convenience,
+2. provider-neutral contracts over package-specific shortcuts,
+3. maintainable structure over short-term shortcuts.

graphfakos-0.0.1/CONTRIBUTING.md

@@ -0,0 +1,149 @@
+# Contributing to GraphFakos
+
+Thanks for contributing.
+
+## Before Coding
+
+Read these docs before coding:
+
+1. [README.md](./README.md)
+2. [API_COMPATIBILITY.md](./API_COMPATIBILITY.md)
+3. [docs/README.md](./docs/README.md)
+4. [docs/source-tree-owner-map.md](./docs/source-tree-owner-map.md)
+5. [RELEASING.md](./RELEASING.md) when the work affects packaging or release
+   behavior
+
+Treat the package README and API compatibility policy as the stable public
+contract. GraphFakos is a viewer and adapter-contract package, not a memory
+store, source ingester, graph builder, or runtime policy engine.
+
+## Quick Start
+
+1. Fork and create a branch.
+2. Make focused changes.
+3. Add or update tests.
+4. Open a PR with a clear summary.
+
+## Repository Layout
+
+```text
+graphfakos/
+├── src/graphfakos/             # public package shipped on PyPI
+│   ├── adapters/               # fixture and example providers
+│   ├── testing/                # reusable viewer assertions
+│   ├── ui/                     # dependency-free graph viewer rendering
+│   ├── contracts.py            # public adapter/DTO contract exports
+│   ├── models.py               # provider-neutral DTOs
+│   ├── provider.py             # provider protocol and validation helpers
+│   ├── render.py               # public rendering exports
+│   ├── server.py               # local preview server primitives
+│   └── static.py               # static HTML export helpers
+├── tests/                      # package tests and contract fixtures
+├── docs/                       # public package-local docs
+├── pyproject.toml
+└── scripts/release_check.py    # package release smoke
+```
+
+The public wheel is everything under `src/graphfakos/`. Tests, package docs,
+and release tooling support the package but do not enlarge the runtime API
+beyond `README.md`, `API_COMPATIBILITY.md`, and `docs/`.
+
+## Setup
+
+Requires Python 3.11+.
+
+```bash
+# 1. Clone and enter the repo
+git clone https://github.com/openminion/graphfakos.git graphfakos
+cd graphfakos
+
+# 2. Create and activate a virtualenv
+python3.11 -m venv .venv
+source .venv/bin/activate
+
+# 3. Install in editable mode with dev extras
+make dev-install
+```
+
+## Running Tests
+
+```bash
+# Full package test suite
+make test
+
+# Full local quality gate
+make check
+
+# Release/install smoke
+make release-check
+```
+
+If you need a narrower loop while iterating, run `python3.11 -m pytest -q
+tests/<target>` inside the activated virtualenv.
+
+## Running Lint and Formatting
+
+```bash
+# Lint only
+make lint
+
+# Check formatting without rewriting files
+make format-check
+
+# Apply formatting and autofixes
+make fix
+```
+
+## Development Basics
+
+1. Follow the existing typed, deterministic package style.
+2. Keep provider-specific graph semantics outside GraphFakos core.
+3. Add or update tests for any behavior change.
+4. Keep static export working as the baseline viewer mode.
+5. Do not add hidden imports from Sophiagraph, PragmaGraph, or OpenMinion.
+6. Do not bundle unrelated refactors into the same PR.
+7. Keep public docs portable and copy/paste friendly.
+
+Preferred PR shape:
+
+1. `Title`
+   - short and literal, for example `Add path controls to graph viewer`
+2. `Description`
+   - `- add ...`
+   - `- align ...`
+   - `- polish ...`
+3. `Validation`
+   - `- <command>`
+   - `- <command>`
+
+## Submitting a Pull Request
+
+1. Fork and create a branch from `main`.
+2. Make your change; add or update tests; run the relevant local validation.
+3. Open a PR with a clear summary. In the description, include what changed,
+   why, and the exact commands you ran for validation.
+4. Keep PRs small and reviewable.
+5. Do not bundle unrelated refactors into the same PR.
+
+## Legal Basics
+
+1. You keep ownership of your contributions.
+2. By submitting a contribution, you license it under Apache-2.0.
+3. Apache-2.0 includes a patent license for your contribution, with the standard
+   patent-termination condition in the license text.
+4. Only submit code or content you have the right to contribute.
+5. Do not add third-party code or assets unless their license is compatible and
+   clearly documented.
+6. Project names and logos are not granted for endorsement use.
+7. `graphfakos` is provided on an "as is" basis under the project license.
+8. See [LICENSE](./LICENSE) for the full legal terms, disclaimers, and
+   limitations of liability.
+
+## Security
+
+If you find a security issue, do not open a public issue with exploit details.
+Use the project security reporting process.
+
+## Code of Conduct
+
+By participating, you agree to follow [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).

graphfakos-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.

graphfakos-0.0.1/MANIFEST.in

@@ -0,0 +1,15 @@
+include LICENSE
+include NOTICE
+include CODE_OF_CONDUCT.md
+include CODE_QUALITY.md
+include CONTRIBUTING.md
+include SECURITY.md
+include SUPPORT.md
+recursive-include scripts *.py
+recursive-include docs *.md
+include API_COMPATIBILITY.md
+include README.md
+include RELEASING.md
+include src/graphfakos/py.typed
+recursive-exclude * __pycache__ *.py[cod]
+prune src/*.egg-info

graphfakos-0.0.1/NOTICE

@@ -0,0 +1,20 @@
+GraphFakos
+Copyright 2026 GraphFakos Contributors
+
+This product includes software developed by GraphFakos contributors.
+
+Source code is licensed under the Apache License, Version 2.0. The software
+license grants copyright permissions only; it does not grant any right to use
+OpenMinion, Sophiagraph, PragmaGraph, GraphFakos, or related names, logos,
+branding, website identity, or social identity except as required for truthful
+and customary attribution.
+
+Forks, clones, and derivative distributions must not state or imply that they
+are the official GraphFakos project or otherwise affiliated with, endorsed by,
+or maintained by GraphFakos, Sophiagraph, PragmaGraph, or OpenMinion
+contributors unless they actually are.
+
+GraphFakos and related package identities have no official token, coin, NFT,
+airdrop, staking program, treasury product, or investment offering. Any use of
+these identities to market or imply a crypto asset, fundraising scheme, or
+investment opportunity is unauthorized and should be treated as a scam.