Improve documentation for consciousness equation parameters

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
documentation

Research direction

Read symthaea-core/src/hdc/consciousness_equation.rs, focusing on ConsciousnessEquationV2 and the ConsciousnessStateV2 fields. Then inspect parameter population under src/cognitive_loop/consciousness_engine/ and consult papers/latex/hai_paper.tex for context. Done means each field has rustdoc covering its role, range, Φ sensitivity, substrate_feasibility interaction, and default rationale; verify with cargo doc -p symthaea-core --no-deps.

Written by the indexing model from the issue text.

Description

documentation good first issue

Summary

The consciousness equation (IIT Φ computation) in symthaea-core/src/hdc/consciousness_equation.rs has many tunable parameters but limited documentation on their effects.

What needs documenting

Add rustdoc comments explaining:

  • Each parameter's role in the Φ computation
  • Valid ranges (many are 0.0–1.0 but some have different semantics)
  • Impact on Φ scores — which parameters are most sensitive
  • Substrate feasibility interaction — how substrate_feasibility modulates the final score
  • Default values and why they were chosen

References

  • Tononi, G. (2004). An information integration theory of consciousness. BMC Neuroscience.
  • Our HAI paper in papers/latex/hai_paper.tex
  • ConsciousnessEquationV2 is the current implementation
  • ConsciousnessStateV2 holds the input parameters

Getting started

  1. Read symthaea-core/src/hdc/consciousness_equation.rs
  2. Look at how parameters are populated in src/cognitive_loop/consciousness_engine/
  3. Add /// doc comments to each field in ConsciousnessStateV2
  4. Verify docs build: cargo doc -p symthaea-core --no-deps
Dominant language
Rust
Stars
9
Forks
1
Avg merge
15m
Merged PRs (30d)
8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Luminous-Dynamics/symthaea

All issues in Luminous-Dynamics/symthaea

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.