Skip to content

Commit babb7e5

Browse files
hummbl-devhummbl-dev
committed
Initial commit: HUMMBL Unified Tier Framework v1.0
- Complete framework document (9.2/10 quality, 1,644 lines) - Core documentation (README, LICENSE, CHANGELOG, etc.) - GitHub Actions automation (markdown-lint, link-checker, spell-check) - Issue and PR templates for community engagement - GitHub Pages landing page - Full professional repository structure Framework Components: - 5 Problem Complexity Tiers (Simple → Super-Wicked) - 5 Learning Progression Tiers (Pre-Learning → Creator) - Base-N Architecture (Base6 → BASE120) - Quantitative wickedness scoring methodology - Evidence from BASE120 validation (Oct 31, 2025) Attribution: - DeepSeek AI (Tier 1-4 descriptions, learning labels) - HUMMBL Systems (Tier 5, scoring, Base-N, validation) - Academic: Levin et al. (2012) super-wicked problems concept Quality Metrics: - Document Quality: 9.2/10 - Legal Protection: Complete - Evidence Integrity: High - Community Ready: Yes Repository includes: - 16 total files - 3 automated workflows - 3 issue templates - 1 PR template - 1 GitHub Pages site Status: Production-ready for public release
0 parents  commit babb7e5

16 files changed

+4414
-0
lines changed

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
---
2+
name: Bug Report
3+
about: Report an error, inconsistency, or broken link in the framework
4+
title: '[BUG] '
5+
labels: bug
6+
assignees: ''
7+
---
8+
9+
## Bug Description
10+
11+
**Clear and concise description of the bug:**
12+
13+
14+
## Location
15+
16+
**Where is the bug located?**
17+
18+
- **File:** (e.g., HUMMBL_Unified_Tier_Framework_v1.0.md)
19+
- **Section:** (e.g., Section 4.2 Tier Classification Formula)
20+
- **Line Number(s):** (if applicable)
21+
- **Link:** (direct link to the section if viewing online)
22+
23+
## Bug Type
24+
25+
**What type of bug is this?** (check all that apply)
26+
27+
- [ ] Typo or spelling error
28+
- [ ] Grammar or syntax error
29+
- [ ] Broken link (external)
30+
- [ ] Broken cross-reference (internal)
31+
- [ ] Incorrect information or data
32+
- [ ] Inconsistency between sections
33+
- [ ] Missing attribution or citation
34+
- [ ] Formatting issue
35+
- [ ] Other (please describe)
36+
37+
## Current Behavior
38+
39+
**What currently happens (incorrect behavior):**
40+
41+
42+
## Expected Behavior
43+
44+
**What should happen instead (correct behavior):**
45+
46+
47+
## Evidence/Context
48+
49+
**Additional context, screenshots, or evidence:**
50+
51+
52+
## Suggested Fix
53+
54+
**If you have a suggestion for how to fix this:**
55+
56+
57+
## Impact
58+
59+
**How does this bug affect users?**
60+
61+
- [ ] Critical - Prevents understanding or use of framework
62+
- [ ] High - Causes confusion or misunderstanding
63+
- [ ] Medium - Minor inconvenience or aesthetic issue
64+
- [ ] Low - Cosmetic only, no functional impact
65+
66+
## Environment
67+
68+
**Where did you encounter this bug?**
69+
70+
- **Viewing Method:** (GitHub web, local clone, PDF export, etc.)
71+
- **Browser/OS:** (if relevant)
72+
- **Framework Version:** (e.g., v1.0.0)
73+
74+
## Additional Information
75+
76+
**Any other relevant information:**
77+
78+
79+
---
80+
81+
**Checklist before submitting:**
82+
83+
- [ ] I have searched existing issues to avoid duplicates
84+
- [ ] I have provided specific location information
85+
- [ ] I have described both current and expected behavior
86+
- [ ] I have assessed the impact level

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
---
2+
name: Feature Request
3+
about: Suggest an enhancement or new content for the framework
4+
title: '[FEATURE] '
5+
labels: enhancement
6+
assignees: ''
7+
---
8+
9+
## Feature Description
10+
11+
**Clear and concise description of the proposed feature:**
12+
13+
14+
## Use Case
15+
16+
**What problem does this feature solve? Who would benefit?**
17+
18+
19+
## Proposed Solution
20+
21+
**Describe your proposed solution or enhancement:**
22+
23+
24+
## Framework Section
25+
26+
**Which section(s) would this affect?** (check all that apply)
27+
28+
- [ ] Section 1: Problem Complexity Tiers
29+
- [ ] Section 2: Learning Progression Tiers
30+
- [ ] Section 3: Base-N Architecture Mapping
31+
- [ ] Section 4: Wickedness Scoring Methodology
32+
- [ ] Section 5: Validation Evidence
33+
- [ ] Section 6: Attribution & IP
34+
- [ ] Section 7: Practical Application Guide
35+
- [ ] Section 8: Implementation Protocols
36+
- [ ] Appendices
37+
- [ ] New section (describe below)
38+
- [ ] Repository/tooling (not framework content)
39+
40+
## Success Criteria
41+
42+
**How would we know this feature is successful?**
43+
44+
1.
45+
2.
46+
3.
47+
48+
## Priority Assessment
49+
50+
**How important is this feature?**
51+
52+
- [ ] Critical - Framework incomplete without it
53+
- [ ] High - Significantly improves framework value
54+
- [ ] Medium - Nice to have, adds value
55+
- [ ] Low - Minor enhancement
56+
57+
## Alternatives Considered
58+
59+
**Have you considered alternative approaches?**
60+
61+
62+
## Additional Context
63+
64+
**Examples, mockups, references, or other context:**
65+
66+
67+
## Implementation Effort
68+
69+
**Your estimate of implementation complexity:**
70+
71+
- [ ] Small - Minor addition or clarification
72+
- [ ] Medium - New subsection or significant content
73+
- [ ] Large - New section or major restructuring
74+
- [ ] Unknown
75+
76+
---
77+
78+
**Checklist before submitting:**
79+
80+
- [ ] I have searched existing issues/features to avoid duplicates
81+
- [ ] I have described a clear use case
82+
- [ ] I have proposed a specific solution
83+
- [ ] I have considered alternatives
84+
- [ ] I understand this may require discussion before implementation

‎.github/ISSUE_TEMPLATE/question.md‎

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
---
2+
name: Question
3+
about: Ask a question about the framework or how to use it
4+
title: '[QUESTION] '
5+
labels: question
6+
assignees: ''
7+
---
8+
9+
## Question
10+
11+
**Your question:**
12+
13+
14+
## Framework Context
15+
16+
**Which part of the framework is your question about?**
17+
18+
- **Section:** (e.g., Section 4 - Wickedness Scoring)
19+
- **Topic:** (e.g., How to score problems with partial information)
20+
- **Specific Reference:** (line numbers, subsections, etc.)
21+
22+
## Background
23+
24+
**What are you trying to accomplish?**
25+
26+
27+
## What You've Already Tried
28+
29+
**Have you:**
30+
31+
- [ ] Read the relevant framework section
32+
- [ ] Checked the Glossary (Appendix A)
33+
- [ ] Reviewed worked examples
34+
- [ ] Searched existing issues/discussions
35+
- [ ] Consulted the Practical Application Guide (Section 7)
36+
37+
**What specifically have you tried or reviewed?**
38+
39+
40+
## Your Current Understanding
41+
42+
**What do you currently understand about this topic?**
43+
44+
45+
## Specific Confusion
46+
47+
**What specifically is unclear or confusing?**
48+
49+
50+
## Use Case (Optional)
51+
52+
**If applicable, describe the specific problem you're trying to solve:**
53+
54+
55+
## Question Type
56+
57+
**What type of question is this?**
58+
59+
- [ ] Clarification - Need better understanding of existing content
60+
- [ ] Application - How to apply framework to specific situation
61+
- [ ] Methodology - Question about scoring or assessment process
62+
- [ ] Interpretation - How to interpret results or recommendations
63+
- [ ] Integration - How to combine with other methodologies
64+
- [ ] Other (describe below)
65+
66+
---
67+
68+
**Note:** For bug reports, use the Bug Report template. For feature requests, use the Feature Request template.

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
# Pull Request
2+
3+
## Description
4+
5+
**Brief description of changes:**
6+
7+
8+
## Type of Change
9+
10+
**What type of change does this PR introduce?** (check all that apply)
11+
12+
- [ ] Bug fix (typo, broken link, incorrect information)
13+
- [ ] Documentation improvement (clarification, additional examples)
14+
- [ ] New content (new section, case study, worked example)
15+
- [ ] Formatting/style improvement
16+
- [ ] Translation
17+
- [ ] Repository/tooling improvement
18+
- [ ] Other (please describe)
19+
20+
## Related Issue
21+
22+
**Does this PR close an existing issue?**
23+
24+
Closes #(issue number)
25+
26+
## Changes Made
27+
28+
**Detailed list of changes:**
29+
30+
-
31+
-
32+
-
33+
34+
## Testing Performed
35+
36+
**How have you tested these changes?**
37+
38+
- [ ] Verified all links work
39+
- [ ] Checked markdown formatting
40+
- [ ] Ran spell check
41+
- [ ] Verified cross-references
42+
- [ ] Reviewed for consistency with existing content
43+
- [ ] Other (describe):
44+
45+
## Screenshots (if applicable)
46+
47+
**Add screenshots to demonstrate changes:**
48+
49+
50+
## Checklist
51+
52+
**Before submitting, ensure you have:**
53+
54+
- [ ] Read the [CONTRIBUTING.md](../CONTRIBUTING.md) guidelines
55+
- [ ] Followed the project style guide
56+
- [ ] Maintained proper attribution (DeepSeek, academic sources, etc.)
57+
- [ ] Tested all changes (links, formatting, etc.)
58+
- [ ] Updated relevant sections (if applicable)
59+
- [ ] Added/updated examples (if applicable)
60+
- [ ] Checked for spelling and grammar errors
61+
- [ ] Ensured changes are focused and minimal
62+
- [ ] Provided clear description of changes
63+
- [ ] Referenced related issues (if applicable)
64+
65+
## Attribution
66+
67+
**If this PR includes content from external sources:**
68+
69+
- [ ] I have properly attributed all sources
70+
- [ ] I have permission to use this content
71+
- [ ] I understand the license requirements
72+
73+
## Additional Notes
74+
75+
**Any additional context or information:**
76+
77+
78+
---
79+
80+
**By submitting this PR, I confirm that:**
81+
82+
- [ ] I have read and agree to the [LICENSE.md](../LICENSE.md) terms
83+
- [ ] I have read and agree to the [CODE_OF_CONDUCT.md](../CODE_OF_CONDUCT.md)
84+
- [ ] My contributions are my own work or properly attributed
85+
- [ ] I grant permission for my contributions to be used under the project license

0 commit comments

Comments
 (0)