Skip to content

Add QuMat neutrosophic foundation docs#1373

Open
SeCuReDmE-main-dev wants to merge 1 commit into
apache:mainfrom
SeCuReDmE-main-dev:docs/mahout-neutro-case-foundation
Open

Add QuMat neutrosophic foundation docs#1373
SeCuReDmE-main-dev wants to merge 1 commit into
apache:mainfrom
SeCuReDmE-main-dev:docs/mahout-neutro-case-foundation

Conversation

@SeCuReDmE-main-dev
Copy link
Copy Markdown

@SeCuReDmE-main-dev SeCuReDmE-main-dev commented Jun 1, 2026

Summary

  • add the phase-1 documentation foundation for an experimental neutrosophic operator layer in QuMat
  • ground the proposal in published sources and official Mahout context
  • add a citation gate so future implementation slices stay explicit about what is source-backed, what is a local design extension, and what is still unsupported
  • link the RFC pack from the QuMat docs index so the discussion has a stable public entrypoint

Details

This PR is the single public Phase 1 anchor for the experimental neutrosophic discussion tied to apache/mahout#1372.

Its scope is intentionally documentation-only. It does not change QuMat runtime behavior, backend dispatch, or production circuit semantics. Its purpose is to make the discussion reviewable in public while the implementation branches remain protected on the case-study side.

This branch adds:

  • an RFC for a conservative experimental neutrosophic operator-layer discussion
  • an academic bibliography restricted to published sources and official Mahout context
  • an implementation-to-citation map that separates source-backed items from local design extensions
  • docs index links so the RFC pack is reachable from the QuMat docs surface

Current implementation posture:

Conservative constraints for the public Mahout surface:

  • no production backend rewrite in the first pass
  • no public API break for current QuMat users
  • no claim that qiskit, cirq, or amazon_braket natively execute a 3-state neutrosophic carrier
  • no additional upstream implementation PRs unless maintainers indicate interest in that direction

Validation

  • reviewed rendered-style link targets and relative doc paths
  • verified the docs are linked from docs/index.md
  • confirmed this branch changes documentation only and does not alter QuMat runtime behavior

RFC

@400Ping
Copy link
Copy Markdown
Member

400Ping commented Jun 1, 2026

Don't have context about this, will need some time to understand this.

@SeCuReDmE-main-dev
Copy link
Copy Markdown
Author

Status update: the 6-branch engineering program now exists as protected branches on the case-study repository side, while this PR remains the only upstream-facing Phase 1 anchor.

Protected local branches:

Local experimental validation currently passes through the comparison-harness layer. No additional upstream implementation PRs are planned unless maintainers indicate interest in that direction.

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.

2 participants