Changes for page Contributor Processes

Last modified by Robert Schaub on 2026/02/08 08:29

From 1.2 to 1.1

From version 1.3

edited by Robert Schaub
on 2026/02/08 08:29

Change comment: Renamed back-links.

To version 1.2

edited by Robert Schaub
on 2026/02/08 08:28

Change comment: Update document after refactoring.

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -1,12 +1,8 @@
  = Contributor Processes =
--
  == 1. Purpose ==
--
  This page explains how contributors improve **the system that evaluates claims**, not the claims themselves.
  **Key Principle**: AKEL makes content decisions. Contributors improve the algorithms, policies, and infrastructure that enable AKEL to make better decisions.
--
  == 2. What Contributors Do ==
--
  Contributors work on **system improvements**, not content review:
  ✅ **Algorithm improvements**: Better evidence detection, improved source scoring, enhanced contradiction detection
  ✅ **Policy proposals**: Risk tier definitions, domain-specific rules, moderation criteria
@@ -13,9 +13,7 @@
  ✅ **Infrastructure**: Performance optimization, scaling improvements, monitoring tools
  ✅ **Documentation**: User guides, API docs, architecture documentation
  ✅ **Testing**: A/B tests, regression tests, performance benchmarks
--
  == 3. What Contributors Do NOT Do ==
--
  ❌ **Review individual claims for correctness** - That's AKEL's job
  ❌ **Override AKEL verdicts** - Fix the algorithm, not the output
  ❌ **Manually adjust source scores** - Improve scoring rules systematically
@@ -22,58 +22,39 @@
  ❌ **Act as approval gates** - Defeats purpose of automation
  ❌ **Make ad-hoc content decisions** - All content decisions must be algorithmic
  **If you think AKEL made a mistake**: Don't fix that one case. Fix the algorithm so it handles all similar cases correctly.
--
  == 4. Contributor Journey ==
--
  === 4.1 Visitor ===
--
  * Reads documentation
  * Explores repositories
  * May open issues reporting bugs or suggesting improvements
--
  === 4.2 New Contributor ===
--
  * First contributions: Documentation fixes, clarifications, minor improvements
  * Learns: System architecture, RFC process, testing procedures
  * Builds: Understanding of FactHarbor principles
--
  === 4.3 Regular Contributor ===
--
  * Contributes regularly to system improvements
  * Follows project rules and RFC process
  * Track record of quality contributions
--
  === 4.4 Trusted Contributor ===
--
  * Extensive track record of high-quality work
  * Deep understanding of system architecture
  * Can review others' contributions
  * Participates in technical decisions
--
  === 4.5 Maintainer ===
--
  * Approves system changes within domain
  * Technical Coordinator or designated by them
  * Authority over specific system components
  * Accountable for system performance in domain
--
  === 4.6 Moderator (Separate Track) ===
--
  * Handles AKEL-flagged escalations
  * Focuses on abuse, manipulation, system gaming
  * Proposes detection improvements
  * Does NOT review content for correctness
--
  == 4.7 Contributor Roles and Trust Levels ==
--
  The following describes the different levels of contributors and their permissions:
--
  == 1. Purpose ==
--
  This page describes how people can participate in FactHarbor and how responsibilities grow with trust and experience.
--
  == 2. Contributor Journey ==
--
 . **Visitor** – explores the platform, reads documentation, may raise questions.
 . **New Contributor** – submits first improvements (typo fixes, small clarifications, new issues).
 . **Contributor** – contributes regularly and follows project conventions.
@@ -81,40 +81,28 @@
 . **Contributor** – reviews changes for correctness, neutrality, and process compliance.
 . **Moderator** – focuses on behaviour, tone, and conflict moderation.
 . **Trusted Contributor (optional)** – offers domain expertise without changing governance authority.
--
  == 3. Principles ==
--
  * Low barrier to entry for new contributors.
  * Transparent criteria for gaining and losing responsibilities.
  * Clear separation between content quality review and behavioural moderation.
  * Documented processes for escalation and appeal.
--
  == 4. Processes ==
--
  Typical contributor processes include:
--
  * proposal and review of documentation or code changes
  * reporting and triaging issues or suspected errors
  * moderation of discussions and conflict resolution
  * onboarding support for new contributors.
  Details of the process steps are aligned with the [[Open Source Model and Licensing>>FactHarbor.Organisation.Open Source Model and Licensing]] and [[Decision Processes>>FactHarbor.Organisation.Decision-Processes]] pages.
--
  == 5. System Improvement Workflow ==
--
  === 5.1 Identify Issue ===
--
  **Sources**:
--
  * Performance metrics dashboard shows anomaly
  * User feedback reveals pattern
  * AKEL processing logs show systematic error
  * Code review identifies technical debt
  **Key**: Focus on PATTERNS, not individual cases.
--
  === 5.2 Diagnose Root Cause ===
--
  **Analysis methods**:
--
  * Run experiments in test environment
  * Analyze AKEL decision patterns
  * Review algorithm parameters
@@ -121,9 +121,7 @@
  * Check training data quality
  * Profile performance bottlenecks
  **Output**: Clear understanding of systematic issue.
--
  === 5.3 Propose Solution (RFC) ===
--
  **Create Request for Comments (RFC)**:
  **RFC Template**:
  ```
@@ -141,23 +141,17 @@
  How will this be validated before full deployment?
  ## Rollback Plan
  If this doesn't work, how do we revert?
--```##
--
++```
  === 5.4 Community Discussion ===
--
  **RFC review period**: 7-appropriate time period (based on impact)
  **Participants**:
--
  * Other contributors comment
  * Maintainers review for feasibility
  * Technical Coordinator for architectural impact
  * Governing Team for policy implications
  **Goal**: Surface concerns, improve proposal, build consensus
--
  === 5.5 Test & Validate ===
--
  **Required before approval**:
--
  * ✅ Deploy to test environment
  * ✅ Run on historical data (regression test)
  * ✅ Measure impact on key metrics
@@ -168,11 +168,8 @@
  * Doesn't break existing functionality
  * Metrics improve or remain stable
  * No unacceptable trade-offs
--
  === 5.6 Review & Approval ===
--
  **Review by**:
--
  * **Technical changes**: Technical Coordinator (or designated Maintainer)
  * **Policy changes**: Governing Team (consent-based decision)
  * **Infrastructure**: Technical Coordinator
@@ -182,11 +182,8 @@
  * Test results positive
  * No principled objections (for consent-based decisions)
  * Aligns with FactHarbor principles
--
  === 5.7 Deploy & Monitor ===
--
  **Deployment strategy**:
--
  * Gradual rollout (canary deployment)
  * Monitor key metrics closely
  * Ready to rollback if problems
@@ -197,23 +197,16 @@
  * No unexpected side effects
  * User feedback positive
  * System stability maintained
--
  === 5.8 Evaluate & Iterate ===
--
  **Post-deployment review**:
--
  * Did metrics improve as expected?
  * Any unexpected effects?
  * What did we learn?
  * What should we do differently next time?
  **Document learnings**: Update RFC with actual outcomes.
--
  == 6. Contribution Types in Detail ==
--
  === 6.1 Algorithm Improvements ===
--
  **Examples**:
--
  * Better evidence extraction from web pages
  * Improved source reliability scoring
  * Enhanced contradiction detection
@@ -221,11 +221,8 @@
  * More accurate risk classification
  **Process**: RFC → Test → Review → Deploy → Monitor
  **Skills needed**: Python, ML/AI, data analysis, testing
--
  === 6.2 Policy Proposals ===
--
  **Examples**:
--
  * Risk tier definition refinements
  * New domain-specific guidelines
  * Moderation criteria updates
@@ -232,11 +232,8 @@
  * Community behavior standards
  **Process**: RFC → Community discussion → Governing Team consent → Deploy → Monitor
  **Skills needed**: Domain knowledge, policy writing, ethics
--
  === 6.3 Infrastructure Improvements ===
--
  **Examples**:
--
  * Database query optimization
  * Caching strategy improvements
  * Monitoring tool enhancements
@@ -244,11 +244,8 @@
  * Scaling improvements
  **Process**: RFC → Test → Technical Coordinator review → Deploy → Monitor
  **Skills needed**: DevOps, databases, system architecture, performance tuning
--
  === 6.4 Documentation ===
--
  **Examples**:
--
  * User guides
  * API documentation
  * Architecture documentation
@@ -256,23 +256,16 @@
  * Tutorial videos
  **Process**: Draft → Community feedback → Community Coordinator review → Publish
  **Skills needed**: Technical writing, understanding of FactHarbor
--
  == 7. Quality Standards ==
--
  === 7.1 Code Quality ===
--
  **Required**:
--
  * ✅ Follows project coding standards
  * ✅ Includes tests
  * ✅ Documented (code comments + docs update)
  * ✅ Passes CI/CD checks
  * ✅ Reviewed by maintainer
--
  === 7.2 Testing Requirements ===
--
  **Algorithm changes**:
--
  * Unit tests
  * Integration tests
  * Regression tests on historical data
@@ -281,22 +281,15 @@
  * Validation on test cases
  * Impact analysis on existing claims
  * Edge case coverage
--
  === 7.3 Documentation Requirements ===
--
  **All changes must include**:
--
  * Updated architecture docs (if applicable)
  * Updated API docs (if applicable)
  * Migration guide (if breaking change)
  * Changelog entry
--
  == 8. Handling Disagreements ==
--
  === 8.1 Technical Disagreements ===
--
  **Process**:
--
 . Discuss in RFC comments
 . Present data/evidence
 . Consider trade-offs openly
@@ -303,11 +303,8 @@
 . Technical Coordinator makes final decision (or escalates)
 . Document reasoning
  **Principle**: Data and principles over opinions
--
  === 8.2 Policy Disagreements ===
--
  **Process**:
--
 . Discuss in RFC
 . Clarify principles at stake
 . Consider stakeholder impact
@@ -314,21 +314,14 @@
 . Governing Team uses consent-based decision
 . Document reasoning
  **Principle**: Consent-based (not consensus) - can you support this even if not perfect?
--
  === 8.3 Escalation Path ===
--
  **For unresolved issues**:
--
  * Technical → Technical Coordinator → Governing Team
  * Policy → Governing Team → General Assembly (if fundamental)
  * Behavior → Moderator → Governance Steward → Governing Team
--
  == 9. Behavior Standards ==
--
  === 9.1 Expected Behavior ===
--
  **Contributors are expected to**:
--
  * ✅ Assume good faith
  * ✅ Focus on system improvements, not personal opinions
  * ✅ Support decisions once made (even if you disagreed)
@@ -336,11 +336,8 @@
  * ✅ Document your reasoning
  * ✅ Test thoroughly before proposing
  * ✅ Learn from mistakes
--
  === 9.2 Unacceptable Behavior ===
--
  **Will not be tolerated**:
--
  * ❌ Personal attacks
  * ❌ Harassment or discrimination
  * ❌ Attempting to game the system
@@ -347,21 +347,15 @@
  * ❌ Circumventing the RFC process for significant changes
  * ❌ Deploying untested changes to production
  * ❌ Ignoring feedback without explanation
--
  === 9.3 Enforcement ===
--
  **Process**:
--
  * First offense: Warning + coaching
  * Second offense: Temporary suspension (duration based on severity)
  * Third offense: Permanent ban
  **Severe violations** (harassment, malicious code): Immediate ban
  **Appeal**: To Governance Steward, then Governing Team
--
  == 10. Recognition ==
--
  **Contributors are recognized through**:
--
  * Public acknowledgment in release notes
  * Contribution statistics on profile
  * Special badges for significant contributions
@@ -371,11 +371,8 @@
  * Payment (unless contracted separately)
  * Automatic role promotions
  * Special privileges in content decisions (there are none)
--
  == 11. Getting Started ==
--
  **New contributors should**:
--
 . Read this page + [[Organisational Model>>FactHarbor.Organisation.Organisational-Model]]
 . Join community forum
 . Review open issues labeled "good first issue"
@@ -385,17 +385,14 @@
 . Participate in discussions
 . Build track record
  **Resources**:
--
  * Developer guide: [Coming soon]
  * RFC template: [In repository]
  * Community forum: [Link]
  * Slack/Discord: [Link]
  ---
--**Remember**: You improve the SYSTEM. AKEL improves the CONTENT.--
--
++**Remember**: You improve the SYSTEM. AKEL improves the CONTENT.
  == 12. Related Pages ==
--
  * [[Contributor Processes>>FactHarbor.Organisation.Contributor-Processes]] - Roles and trust levels
--* [[Governance>>Archive.FactHarbor 2026\.02\.08.Organisation.Governance.WebHome]] - Decision-making structure
++* [[Governance>>FactHarbor.Organisation.Governance.WebHome]] - Decision-making structure
  * [[Organisational Model>>FactHarbor.Organisation.Organisational-Model]] - Team structure
  * [[Decision Processes>>FactHarbor.Organisation.Decision-Processes]] - How decisions are made

Changes for page Contributor Processes

Summary

Details

Navigation

Need help?