Skip to content

docs: simplify KEYSTONE README for non-technical readers - #2

Merged
SWORDIntel merged 5 commits into
mainfrom
docs/executive-readme
Aug 30, 2026
Merged

docs: simplify KEYSTONE README for non-technical readers#2
SWORDIntel merged 5 commits into
mainfrom
docs/executive-readme

Conversation

@SWORDIntel

Copy link
Copy Markdown
Owner

Reworks the root README around business value and progressive disclosure.

Key changes:

  • leads with operational/business benefits rather than implementation mechanics;
  • explicitly states that KEYSTONE is modular and can be adopted component-by-component;
  • retains concise architecture/QIHSE diagrams and a technical snapshot;
  • keeps only a defensible same-host benchmark comparison in the front page;
  • moves backend-selection, execution-path, feature-matrix, memory and pipeline detail into docs/TECHNICAL_OVERVIEW.md;
  • adds docs/README.md as a documentation map;
  • removes the stale ROADMAP.md link from STATUS_SUMMARY.md.

The root README is reduced by 403 lines while preserving technical credibility and links to the deeper material.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0f0dc007d2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/README.md
Comment on lines +14 to +15
| [ACCELERATOR_CONTRACT.md](ACCELERATOR_CONTRACT.md) | Requirements a GPU/NPU/other accelerator backend must satisfy before it is treated as supported. |
| [TELEMETRY_PROCESSOR.md](TELEMETRY_PROCESSOR.md) | Telemetry processor implementation and usage. |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve the Python SDK entry point in the documentation map

The rewrite removes the previous Python SDK installation and usage section, but this new documentation map does not replace it. A repo-wide search of README.md and docs/ now finds no mention of Python, the keystone-sdk package, or pip install -e python, even though python/setup.py and the public SDK remain present. Python consumers therefore lose the only discoverable installation and API entry point; add a Python SDK document or retain a concise link and install command here.

Useful? React with 👍 / 👎.

Comment thread README.md
Comment on lines +141 to +143
1. **No requirement for specialized accelerator hardware.** The current core runs on CPU.
2. **Optional acceleration stays optional.** OpenMP, Fortran, SIMD paths, archive support, classification, and QIHSE integration can be selected independently.
3. **Backend choice is observable.** The runtime exposes whether a decision came from a fast path, measurement, cache, or fallback rather than hiding the execution path.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Clarify that classification is not independently selectable

For deployments using this statement to build a minimal core library, classification cannot currently be selected independently: the Makefile unconditionally adds src/dsmil_model_bridge.c and src/dsmil_micro_model.c, and exposes no classification feature switch. This makes the new deployment guarantee inaccurate; either gate those sources behind a build option or clarify that classification is optional only at API/runtime use, not at build time.

Useful? React with 👍 / 👎.

@SWORDIntel
SWORDIntel merged commit 6b89d62 into main Aug 30, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant