Integrate concept philosophy into manuals - #10
Conversation
|
Warning Rate limit exceeded@koriym has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 18 minutes and 50 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (3)
WalkthroughThis PR updates English and Japanese manuals to reframe terminology from "Doing" to "Being" (Immanence/Transcendence), adds Log-Driven Development (LDD) docs in both languages, adjusts manual navigation to surface a previously hidden chapter, and tweaks a CI workflow trigger. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes
Possibly related PRs
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (6)
manuals/1.0/en/01-overview.md(2 hunks)manuals/1.0/en/02-input-classes.md(3 hunks)manuals/1.0/en/03-being-classes.md(4 hunks)manuals/1.0/en/04-final-objects.md(4 hunks)manuals/1.0/en/12-philosophy-behind.md(1 hunks)manuals/1.0/en/13-vision-ldd.md(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
manuals/1.0/@(en|ja)/**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
manuals/1.0/@(en|ja)/**/*.md: Place new manual pages as Markdown under manuals/1.0/en/ or manuals/1.0/ja/
Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Use .html permalinks for cross-links in content (avoid linking to .md)
Files:
manuals/1.0/en/12-philosophy-behind.mdmanuals/1.0/en/13-vision-ldd.mdmanuals/1.0/en/04-final-objects.mdmanuals/1.0/en/03-being-classes.mdmanuals/1.0/en/02-input-classes.mdmanuals/1.0/en/01-overview.md
🪛 LanguageTool
manuals/1.0/en/12-philosophy-behind.md
[style] ~221-~221: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “reason” or “purpose”.
Context: ...son->validate($email); } } ``` ### Raison d'être French for "reason for being". The Rea...
(RAISON_D_ÊTRE)
[style] ~225-~225: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “reason” or “purpose”.
Context: ...be that existence: - ValidatedUser's raison d'être → Validation capability - SavedUser's...
(RAISON_D_ÊTRE)
[style] ~226-~226: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “reason” or “purpose”.
Context: ...→ Validation capability - SavedUser's raison d'être → Saving capability - DeletedUser's r...
(RAISON_D_ÊTRE)
[style] ~227-~227: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “reason” or “purpose”.
Context: ...e → Saving capability - DeletedUser's raison d'être → Deletion capability Each existence h...
(RAISON_D_ÊTRE)
[grammar] ~376-~376: Ensure spelling is correct
Context: ...lution of Programming ### Evolution of Paradeigm Looking at the evolution of programming ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
manuals/1.0/en/13-vision-ldd.md
[style] ~64-~64: ‘exactly the same’ might be wordy. Consider a shorter alternative.
Context: ...g in, the system can Reproduce (Replay) exactly the same metamorphosis process. ## Conclusion: ...
(EN_WORDINESS_PREMIUM_EXACTLY_THE_SAME)
manuals/1.0/en/04-final-objects.md
[style] ~158-~158: Consider an alternative for the overused word “exactly”.
Context: ...essential value of our system. This is exactly the destination of programming that Be ...
(EXACTLY_PRECISELY)
manuals/1.0/en/03-being-classes.md
[style] ~42-~42: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...> Objects are reborn into the self they want to be, according to their own will (type d...
(REP_WANT_TO_VB)
[style] ~70-~70: Consider using a different adverb to strengthen your wording.
Context: ...he ingredients are the same, it becomes a completely new existence. - Immanent Factor: ...
(COMPLETELY_ENTIRELY)
[style] ~110-~110: Consider an alternative for the overused word “exactly”.
Context: ...formation process in the constructor is exactly the realization of Entelechy. `OrderCal...
(EXACTLY_PRECISELY)
[style] ~110-~110: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...d user. Each class becomes the "self it wants to be" in the constructor. In Be Framework...
(REP_WANT_TO_VB)
manuals/1.0/en/01-overview.md
[style] ~11-~11: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...objects to transform into the self they want to be, by their own will. Marcel Proust s...
(REP_WANT_TO_VB)
[style] ~16-~16: ‘In Search of’ might be wordy. Consider a shorter alternative.
Context: ...es. > > —Marcel Proust, 'The Prisoner' (In Search of Lost Time, Volume 5) 1923 ### Why Not ...
(EN_WORDINESS_PREMIUM_IN_SEARCH_OF)
[style] ~25-~25: Consider using a different adverb to strengthen your wording.
Context: ... system by itself. Be Framework adopts a completely different approach, incorporating the p...
(COMPLETELY_ENTIRELY)
[grammar] ~25-~25: Ensure spelling is correct
Context: ...ere one abandons artifice (control) and entrusts things to proceed to their natural stat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: claude-review
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
manuals/1.0/en/03-being-classes.md (2)
41-42: Reduce repetition of "the self they want to be."The phrase appears twice in close proximity (lines 41–42 and again at line 110), weakening the writing. Consider varying the phrasing in one or both instances.
70-70: Consider varying word choice for "completely" and "exactly."These adverbs appear in the prose (lines 70 and 110) and could be strengthened or replaced with more precise language to enhance clarity and avoid repetition.
Also applies to: 110-110
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
manuals/1.0/en/02-input-classes.md(3 hunks)manuals/1.0/en/03-being-classes.md(4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- manuals/1.0/en/02-input-classes.md
🧰 Additional context used
📓 Path-based instructions (1)
manuals/1.0/@(en|ja)/**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
manuals/1.0/@(en|ja)/**/*.md: Place new manual pages as Markdown under manuals/1.0/en/ or manuals/1.0/ja/
Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Use .html permalinks for cross-links in content (avoid linking to .md)
Files:
manuals/1.0/en/03-being-classes.md
🪛 LanguageTool
manuals/1.0/en/03-being-classes.md
[style] ~42-~42: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...> Objects are reborn into the self they want to be, according to their own will (type d...
(REP_WANT_TO_VB)
[style] ~70-~70: Consider using a different adverb to strengthen your wording.
Context: ...he ingredients are the same, it becomes a completely new existence. - Immanent Factor: ...
(COMPLETELY_ENTIRELY)
[style] ~110-~110: Consider an alternative for the overused word “exactly”.
Context: ...formation process in the constructor is exactly the realization of Entelechy. `OrderCal...
(EXACTLY_PRECISELY)
[style] ~110-~110: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...d user. Each class becomes the "self it wants to be" in the constructor. In Be Framework...
(REP_WANT_TO_VB)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: claude-review
Pull Request Review: English Translation of Be Framework ManualsOverviewThis PR introduces comprehensive English translations for the Be Framework's core documentation, focusing on ontological programming concepts. The work demonstrates strong philosophical depth and introduces important concepts like Wu Wei, Temporal Being, and Log-Driven Development. Positive Aspects ✅Content Quality
Documentation Style
Issues & Concerns 🔍1. English Language Quality (High Priority)Several grammatical issues and awkward phrasings that affect clarity: In 01-overview.md:81 Should be: "What you cannot do is simply not executable" (missing negation) In 02-input-classes.md:19 Better: "This contains only those elements that the object itself possesses" In 03-being-classes.md:28 The metaphor shift from technical to personal ("they shape me") is confusing. Consider revising for consistency. 2. Navigation System Issue (High Priority)The navigation file excludes File: {% unless item.path contains "/index.md" or item.path contains "/convention/" or item.path contains "12-philosophy-behind.md" %}Problem: Chapter 12 (Philosophy Behind) won't appear in the navigation menu, but Chapter 13 (Vision LDD) will. This seems inconsistent. Recommendation:
3. Link Consistency Issues (Medium Priority)Mixed link formats across files: 02-input-classes.md:77 uses Jekyll link tag: [Being Classes]({% link manuals/1.0/en/03-being-classes.md %})01-overview.md:107 uses relative_url filter: [Input Classes]({{ '/manuals/1.0/en/02-input-classes.html' | relative_url }})Recommendation: According to CLAUDE.md guidelines, prefer
Standardize to: 4. Translation Consistency (Low Priority)Some inconsistencies in terminology:
5. Technical Accuracy (Medium Priority)In 13-vision-ldd.md:76 While poetic, this conclusion could be stronger by connecting back to practical benefits for developers. 6. Code Example Verification (Medium Priority)The PR doesn't include:
Recommendation: Consider adding a CI check to validate PHP syntax in code blocks. Security Considerations 🔒No security concerns identified. This is purely documentation with no executable code or configuration changes. Performance Considerations ⚡No performance impact. Jekyll will rebuild static pages efficiently. Test Coverage 🧪Missing:
Recommendations:
Suggestions for Improvement 💡Immediate Fixes Needed:
Future Enhancements:
ConclusionThis is valuable work that brings Be Framework's unique philosophy to English-speaking developers. The core concepts are well-explained and the documentation structure is solid. Recommendation: ✅ Approve with minor revisions The issues identified are mostly minor language polishing and consistency improvements. The most critical item is the navigation configuration for chapter 12, which should be addressed before merge. Estimated effort to address: 1-2 hours for language fixes and link standardization. Great work on this translation! The philosophical depth and clear examples will help developers understand this unique approach to programming. 🎉 |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
manuals/1.0/en/04-final-objects.md (1)
158-158: Consider revising "exactly" for concision.The word "exactly" on Line 158 is flagged as overused in the prose. The sentence "This is exactly the destination of programming..." could be more concise: "This is the destination of programming that Be Framework aims for..."
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
manuals/1.0/en/04-final-objects.md(4 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
manuals/1.0/@(en|ja)/**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
manuals/1.0/@(en|ja)/**/*.md: Place new manual pages as Markdown under manuals/1.0/en/ or manuals/1.0/ja/
Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Use .html permalinks for cross-links in content (avoid linking to .md)
Files:
manuals/1.0/en/04-final-objects.md
🧠 Learnings (1)
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Use .html permalinks for cross-links in content (avoid linking to .md)
Applied to files:
manuals/1.0/en/04-final-objects.md
🪛 LanguageTool
manuals/1.0/en/04-final-objects.md
[style] ~158-~158: Consider an alternative for the overused word “exactly”.
Context: ...essential value of our system. This is exactly the destination of programming that Be ...
(EXACTLY_PRECISELY)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: claude-review
🔇 Additional comments (1)
manuals/1.0/en/04-final-objects.md (1)
162-162: Verify cross-link format for consistency with other manuals.Line 162 uses a relative markdown link path, which differs from the format suggested in the previous review. The extension has been correctly updated to
.html, but the format should be verified against other manual pages to ensure consistency across the documentation site.The past review suggested using the
relative_urlfilter pattern:{{ '/manuals/1.0/en/05-metamorphosis-patterns.html' | relative_url }}. Please confirm whether the current markdown link format[Metamorphosis](./05-metamorphosis-patterns.html)aligns with how other manual pages handle cross-links, or if the filter-based format is required by the site builder.Alternatively, if the relative path format is the accepted approach, consider standardizing to use the full path with
relative_urlfor better portability across environments.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
manuals/1.0/en/01-overview.md (1)
107-107: Cross-link format is valid, though inconsistent with other files.The Liquid syntax
{{ '/manuals/1.0/en/02-input-classes.html' | relative_url }}is valid and uses the required.htmlextension. However, other files in this PR use the simpler relative path format (e.g.,./02-input-classes.html). Consider standardizing to one format across all manual pages for consistency.Optional: Apply this diff to match the format used in other manual files:
-Let's learn from the foundation. Everything starts from [Input Classes]({{ '/manuals/1.0/en/02-input-classes.html' | relative_url }}) → +Let's learn from the foundation. Everything starts from [Input Classes](./02-input-classes.html) →
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (4)
_includes/manuals/1.0/en/contents.html(1 hunks)manuals/1.0/en/01-overview.md(2 hunks)manuals/1.0/en/02-input-classes.md(3 hunks)manuals/1.0/en/03-being-classes.md(4 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
_includes/manuals/1.0/@(en|ja)/contents.html
📄 CodeRabbit inference engine (CLAUDE.md)
Update navigation contents when adding pages (edit _includes/manuals/1.0/[lang]/contents.html)
Files:
_includes/manuals/1.0/en/contents.html
manuals/1.0/@(en|ja)/**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
manuals/1.0/@(en|ja)/**/*.md: Place new manual pages as Markdown under manuals/1.0/en/ or manuals/1.0/ja/
Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Use .html permalinks for cross-links in content (avoid linking to .md)
Files:
manuals/1.0/en/02-input-classes.mdmanuals/1.0/en/01-overview.mdmanuals/1.0/en/03-being-classes.md
🧠 Learnings (3)
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to _includes/manuals/1.0/@(en|ja)/contents.html : Update navigation contents when adding pages (edit _includes/manuals/1.0/[lang]/contents.html)
Applied to files:
_includes/manuals/1.0/en/contents.html
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Applied to files:
_includes/manuals/1.0/en/contents.html
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Use .html permalinks for cross-links in content (avoid linking to .md)
Applied to files:
_includes/manuals/1.0/en/contents.htmlmanuals/1.0/en/03-being-classes.md
🪛 LanguageTool
manuals/1.0/en/01-overview.md
[style] ~11-~11: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...objects to transform into the self they want to be, by their own will. Marcel Proust s...
(REP_WANT_TO_VB)
[style] ~16-~16: ‘In Search of’ might be wordy. Consider a shorter alternative.
Context: ...es. > > —Marcel Proust, 'The Prisoner' (In Search of Lost Time, Volume 5) 1923 ### Why Not ...
(EN_WORDINESS_PREMIUM_IN_SEARCH_OF)
[style] ~25-~25: Consider using a different adverb to strengthen your wording.
Context: ... system by itself. Be Framework adopts a completely different approach, incorporating the p...
(COMPLETELY_ENTIRELY)
[grammar] ~25-~25: Ensure spelling is correct
Context: ...ere one abandons artifice (control) and entrusts things to proceed to their natural stat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
manuals/1.0/en/03-being-classes.md
[style] ~42-~42: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...> Objects are reborn into the self they want to be, according to their own will (type d...
(REP_WANT_TO_VB)
[style] ~70-~70: Consider using a different adverb to strengthen your wording.
Context: ...he ingredients are the same, it becomes a completely new existence. - Immanent Factor: ...
(COMPLETELY_ENTIRELY)
[style] ~110-~110: Consider an alternative for the overused word “exactly”.
Context: ...formation process in the constructor is exactly the realization of Entelechy. `OrderCal...
(EXACTLY_PRECISELY)
[style] ~110-~110: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...d user. Each class becomes the "self it wants to be" in the constructor. In Be Framework...
(REP_WANT_TO_VB)
🪛 markdownlint-cli2 (0.18.1)
manuals/1.0/en/01-overview.md
18-18: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
28-28: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
29-29: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
30-30: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
🔇 Additional comments (7)
manuals/1.0/en/03-being-classes.md (3)
1-43: Philosophical framing effectively introduces core concepts.The Laozi quote, Immanence/Transcendence terminology, and lifecycle narrative ("Birth, Life, Becoming the self you want to be") create a coherent conceptual foundation that aligns well with the PR's objective to communicate the framework's unique philosophy.
44-113: Code examples clearly demonstrate the transformation pattern.The UserProfile and OrderCalculation examples effectively illustrate the Immanence + Transcendence → New Immanence flow. The Entelechy concept is well-explained with appropriate philosophical context that supports the framework's design philosophy.
149-149: Cross-link format is correct.The link uses the
.htmlformat and properly points to the final objects manual, complying with the guideline to use HTML permalinks for cross-links.manuals/1.0/en/02-input-classes.md (2)
1-74: Content structure and terminology are clear and consistent.The "Starting Point" framing with the Heidegger reference effectively introduces Input Classes. The Immanence terminology is used consistently throughout examples, and the distinction from Transcendence is clearly explained.
78-78: Cross-link format is correct.The link properly uses the
.htmlextension and points to the Being Classes manual, maintaining consistency with cross-linking patterns across the documentation.manuals/1.0/en/01-overview.md (1)
34-95: Code examples effectively demonstrate the paradigm shift.The DeletedUser example serves as an effective "hook" to introduce the Be Framework's state-centric approach. The DOING vs BEING comparison and type-based distinction clearly illustrate the practical benefits of the framework's design philosophy.
_includes/manuals/1.0/en/contents.html (1)
21-21: Navigation update correctly exposes the philosophy manual.Removing the exclusion of "12-philosophy-behind.md" from the navigation loop makes the philosophy manual visible to users, which aligns with the PR's objective to communicate the framework's philosophical concepts.
Based on learnings, navigation updates should be made when adding or making pages visible, which is correctly done here.
There was a problem hiding this comment.
Actionable comments posted: 6
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
🟡 Minor comments (17)
concept/dev-docs/psalm-immutability-experiment.md-26-29 (1)
26-29: Add language specification to code blocks.Four code blocks are missing language specification. While these blocks display error messages rather than executable code, Markdown best practices require a language specifier.
Apply this diff to add language specifications:
#### Error Type 1: MutableDependency -``` +```text Be\Framework\SemanticLog\Context\MetamorphosisCloseContext is marked @psalm-immutable but Koriym\SemanticLogger\AbstractContext is not -``` +``` #### Error Type 2: ImpureMethodCall -``` +```text Cannot call a possibly-mutating method ValidationMessageHandler::getMessagesForExceptions from a mutation-free context -``` +``` #### Error Type 3: MissingImmutableAnnotation -``` +```text Be\Framework\SemanticVariable\Errors is marked @psalm-immutable, but Be\Framework\SemanticVariable\NullErrors is not marked @psalm-immutable -``` +``` **`Being` class errors**: -``` +```text Cannot call a possibly-mutating method ReflectionAttribute::newInstance from a mutation-free context Cannot call a possibly-mutating method LoggerInterface::open from a mutation-free context Cannot call a possibly-mutating method BecomingArgumentsInterface::be from a mutation-free context Cannot call a possibly-mutating method ReflectionClass::newInstanceArgs from a mutation-free context -``` +```Also applies to: 34-37, 42-45, 54-59
concept/docs/papers/philosophy/strange-loops-in-code.md-163-177 (1)
163-177: Specify a language for the fenced code block.The ASCII diagram lacks a language identifier. Wrap it with triple backticks followed by a language specifier (e.g.,
text,plaintext, ordiagram).-``` +```text Level 1: Original Code ↓ (executes) Level 2: Semantic Log @@ -175,7 +175,7 @@ Yet somehow, we're back at Level 1, but transformed. -``` +```textconcept/docs/papers/philosophy/strange-loops-in-code.md-593-593 (1)
593-593: Replace emphasis with proper heading or formatting.Line 593 uses emphasis (asterisks) for a poetic closing statement, which violates MD036. Either convert it to a heading or use a different formatting approach.
If intended as a decorative separator or poetic line, consider removing the emphasis or using a thematic line break instead:
-*🦋🎵🔢...∞* +🦋🎵🔢...∞Or if this is meant to be visually distinct section, consider a proper heading or
---separator.manuals/1.0/ja/13-vision-ldd.md-13-15 (1)
13-15: Fix Markdown blockquote formatting.The blockquote contains a blank line (line 14), which violates the MD028
no-blanks-blockquoterule. Consolidate the blockquote by removing the blank line separator.Apply this diff to fix the formatting:
> 「かつて荘周は夢で胡蝶となった。（中略）はたして周が夢で胡蝶となったのか、それとも胡蝶が夢で周となっているのか。」 - > - > —荘子『斉物論』（紀元前4世紀頃） + > + > —荘子『斉物論』（紀元前4世紀頃）Alternatively, if the visual spacing is intentional, use non-blockquote text between the lines or reformat as a code block.
Committable suggestion skipped: line range outside the PR's diff.
concept/dev-docs/philosophical-heritage.md-149-149 (1)
149-149: Minor: Remove redundant phrase for clarity."Moments in time" is slightly redundant since "moments" inherently implies temporal passage.
Apply this diff to improve clarity:
- - Not data containers, but moments in time + - Not data containers, but moments of becoming(Or alternatively: "moments of becoming", "temporal markers", or simply "moments".)
concept/docs/papers/philosophy/ultimate-transparency-article.md-101-103 (1)
101-103: Specify language for fenced code block on line 101.The code block at line 101 (beginning the ascii diagram
Code ⟷ Execution ⟷ Log ⟷ Specification) is missing a language identifier. While the content is text-based, add a language tag for linting compliance:- ``` + ```text Code ⟷ Execution ⟷ Log ⟷ Specification - ``` + ```concept/docs/reference/quotes.md-302-328 (1)
302-328: Fix duplicate section numbering (Sections 22 and 27 each appear twice).The document contains numbering inconsistencies:
- Lines 302–314: Section 22 "Final Transformations"
- Lines 315–328: Section 22 "Creative Vision" (should be 23)
- Lines 385–398: Section 27 "The Ultimate Questions"
- Lines 399–412: Section 27 "Ontological Questions" (should be 28)
Apply this diff to renumber:
- ## 22. Creative Vision + ## 23. Creative Vision- ## 27. Ontological Questions + ## 28. Ontological QuestionsAlso applies to: 385-412
concept/docs/papers/patterns/accept-pattern-ontological-delegation.md-141-141 (1)
141-141: Add language specifier to interface code block.Line 141 should specify the language:
-``` -interface DecisionInterface +```php +interface DecisionInterfaceconcept/docs/reference/influences.md-99-99 (1)
99-99: Fix language consistency issues.This file has several LanguageTool issues affecting clarity:
- Line 99: Fix redundant/unclear phrasing:
-Water embodies the perfect principle of Wu Wei: +Water exemplifies the perfect principle of Wu Wei:
- Lines 147–149: Choose one variant of "dreamed" consistently:
-> *"Once upon a time, I, Zhuangzi, dreamt I was a butterfly, fluttering happily here and there, enjoying life to the full, but never knowing that I was Zhuangzi. Suddenly I awoke, and there I was, veritably Zhuangzi. But I don't know if I am Zhuangzi who dreamed he was a butterfly, or a butterfly dreaming he is Zhuangzi. Between Zhuangzi and a butterfly there must be some distinction! This is called the Transformation of Things."* +*"Once upon a time, I, Zhuangzi, dreamed I was a butterfly, fluttering happily here and there, enjoying life to the full, but never knowing that I was Zhuangzi. Suddenly I awoke, and there I was, veritably Zhuangzi. But I don't know if I am Zhuangzi who dreamed I was a butterfly, or a butterfly dreaming it is Zhuangzi. Between Zhuangzi and a butterfly there must be some distinction! This is called the Transformation of Things."*Use "dreamed" consistently throughout (American English variant) or "dreamt" (British), but not mixed.
Also applies to: 147-149
concept/docs/reference/influences.md-377-377 (1)
377-377: Simplify redundant and awkward phrasing.Several sections contain unnecessary complexity:
- Line 377 (double modal):
-1. **No Independent Objects**: Every object requires Input/Inject conditions +1. **No Independent Objects**: Every object needs Input/Inject conditions
- Line 580 (redundant):
-Ma is **not empty space** - it's **loaded space**, **potential space**, **sacred space**. +Ma is **not empty space** - it's **potential space**, **sacred space**, **pregnant with meaning**.
- Line 1062 (overused "exactly"):
-Whitehead taught that each actual occasion "prehends" (grasps/feels) other occasions. This is exactly how Be Framework constructors work: +Whitehead taught that each actual occasion "prehends" (grasps/feels) other occasions. This is how Be Framework constructors work:Also applies to: 580-580, 1062-1062
concept/docs/papers/philosophy/from-space-to-time.md-25-30 (1)
25-30: Add language specifiers to code blocks.Fenced code blocks should declare the language for syntax highlighting. Lines 25–30 and 54–58 show code blocks without language specifiers:
-``` -Home → About → Products → Contact +```text +Home → About → Products → ContactAnd for lines 54–58:
-```http -GET /user/123 → {"name": "Alice", "age": 30} +```plaintext +GET /user/123 → {"name": "Alice", "age": 30}Also applies to: 54-58
concept/dev-docs/todo.md-23-23 (1)
23-23: Convert emphasis to heading.Line 23 uses emphasis instead of a heading per markdownlint:
-*Focus: Implementing features, not framework maturity milestones* +## Focus: Implementing features, not framework maturity milestonesconcept/docs/papers/patterns/accept-pattern-ontological-delegation.md-354-358 (1)
354-358: Fix redundant phrasing.Line 354 contains redundant language:
### 4. System Flexibility - New experts can be added without modifying existing objects -- Decision criteria can evolve over time +- Decision rules and expert capabilities improve over timeconcept/docs/papers/philosophy/being-paradigm-when-object-gets-its-becoming.md-460-460 (1)
460-460: Use .html permalink in cross-reference.Line 460 references another document using
.mdextension. Per coding guidelines, cross-links within manuals/documentation should use.htmlpermalinks to avoid linking to source files:- **[Being Paradigm Structure](../framework/being-paradigm-structure.md)** - Complete conceptual map + **[Being Paradigm Structure](../framework/being-paradigm-structure.html)** - Complete conceptual mapmanuals/1.0/ja/07-type-driven-metamorphosis.md-120-120 (1)
120-120: Fix unordered list indentation.Lines 120 and 122 use 4-space indentation for nested list items; Markdown convention is 2 spaces (MD007):
-* **Destiny (運命)**: `public readonly Success|Failure $being` - * このプロパティ定義は、「私の未来はこの2つのどちらかである」という予言です。 -* **Self-Discovery (自己発見)**: `$this->being = ...` - * コンストラクタの中で、自身のデータ（Immanence）と環境（Inject）を照らし合わせ、自分が何者になったのかを発見します。 +- **Destiny (運命)**: `public readonly Success|Failure $being` + - このプロパティ定義は、「私の未来はこの2つのどちらかである」という予言です。 +- **Self-Discovery (自己発見)**: `$this->being = ...` + - コンストラクタの中で、自身のデータ（Immanence）と環境（Inject）を照らし合わせ、自分が何者になったのかを発見します。Also applies to: 122-122
manuals/1.0/ja/01-overview.md-27-30 (1)
27-30: Fix unordered list indentation.Lines 28–30 use 4-space indentation for nested list items; Markdown convention is 2 spaces (MD007):
-* Commander (司令官) から Gardener (庭師) へ: - * 司令官（Controller）は、部下（オブジェクト）に「動け」と命令します。 - * 庭師は、植物に命令しません。 - * 植物は、自らの変容のみに関心を持ちます。 +- Commander (司令官) から Gardener (庭師) へ: + - 司令官（Controller）は、部下（オブジェクト）に「動け」と命令します。 + - 庭師は、植物に命令しません。 + - 植物は、自らの変容のみに関心を持ちます。Committable suggestion skipped: line range outside the PR's diff.
manuals/1.0/ja/01-overview.md-18-18 (1)
18-18: Fix heading hierarchy before h3.Line 18 uses
###(h3) without a preceding##(h2). This violates Markdown heading hierarchy (MD001). Add an h2 between the intro content and the h3:制御を手放し、自律的な変容に委ねる。なりたい自分になる。これがBe Frameworkのコアコンセプトです。 +## 新しい考え方への転換 -### なぜ「コントローラー」ではないのか？ (Wu Wei / 無為自然) +### なぜ「コントローラー」ではないのか？ (Wu Wei / 無為自然)
🧹 Nitpick comments (18)
concept/docs/study/merge.sh (3)
13-14: Consider using: >for shellcheck compliance.The syntax
> "$OUTPUT_FILE"is valid bash for file truncation but shellcheck prefers an explicit no-op command.Apply this diff to address the shellcheck hint:
-# Clear the output file -> "$OUTPUT_FILE" +# Clear the output file +: > "$OUTPUT_FILE"
1-11: Consider adding bash strict mode for robustness.The script would benefit from error-handling flags at the start to catch failures early.
Apply this diff to add bash strict mode:
#!/bin/bash +set -euo pipefail # Be Framework - Merge all important files for AI consumption
24-30: Optional: Add check forfilecommand availability.The script relies on the
filecommand but doesn't verify it exists. Whilefileis standard on Unix/Linux, an explicit check would improve portability.Add a check at the script start:
# After the shebang and strict mode flags if ! command -v file &> /dev/null; then echo "Error: 'file' command not found. Please install it." >&2 exit 1 ficoncept/dev-docs/HISTORICAL_NOTE.md (1)
25-27: Consider adding language identifier to fenced code block.The code block showing repository paths would benefit from a language identifier for better syntax highlighting and accessibility.
Apply this diff:
-``` +```text Current: github.com/koriym/be-framework (experimental/learning) Future: github.com/be-framework/be (production)</blockquote></details> <details> <summary>concept/docs/papers/philosophy/ontological-programming-paper.md (1)</summary><blockquote> `540-598`: **Consolidate repetitive philosophical sections to reduce redundancy.** Section 10 (Philosophical Implications) covers overlapping ground in subsections 10.3, 10.4, and 10.6. The "From Doing to Being" progression appears twice (10.3 and 10.6 both cover the conceptual evolution, and 10.1-10.5 discuss related themes). Consider consolidating into a more concise treatment while preserving the distinctive insights of each subsection. Example structure: - 10.1: Programming as Worldbuilding (keep as-is) - 10.2: End of Defensive Programming (keep as-is) - 10.3: Correctness by Construction (keep as-is) - (Consolidate 10.4–10.6 into a unified section on the evolution of control flow and names) </blockquote></details> <details> <summary>concept/docs/papers/philosophy/temporal-programming-revolution.md (1)</summary><blockquote> `296-392`: **Reorder philosophical foundations section for better flow.** The Philosophical Foundations section jumps between Heraclitus (order: 300–322), Buddha (324–365), Whitehead (367–392), and back to implications. Consider reorganizing to follow a temporal or conceptual progression rather than historical chronology. For example: 1. Heraclitean Flux (foundational principle of change) 2. Process Philosophy: Whitehead (mathematical/systematic formalization) 3. Buddhist Impermanence (contemplative perspective) This would create a progression from observation → theory → wisdom, rather than the current scattered approach. </blockquote></details> <details> <summary>concept/docs/reference/influences.md (1)</summary><blockquote> `582-596`: **Reduce sentence-initial repetition for better flow.** Lines 582–596 have three successive sentences beginning with "Ma is": ```diff ##### Ma in Programming: The Space Between Constructors **Traditional Programming (No Ma)**:(code)
-Be Framework (Rich Ma):
-```php
-UserInput
- ║ ← Ma: The space where validation prepares to happen
- ║ The pause before becoming
- ║ Potential waiting to actualize
- ▼
-ValidatedUser- ║ ← Ma: The space where persistence gathers itself
- ║ The breath between validation and saving
+**Be Framework (Rich Ma)**: Introducing intentional pauses in the transformation chain +```php +UserInput + ║ ← Ma: The space where validation prepares to happen + ║ The pause before becoming + ║ Potential waiting to actualizeThis improves readability while preserving the poetic intent.
concept/docs/papers/patterns/unix-pipes-vs-be-framework.md (1)
260-265: Add language specifier to code block at line 261.The code block lacks a language identifier. Change the opening fence to specify the language:
- ``` + ```bash # Can pipe anything to anything date | wc -c ls | grep ".txt" - ``` + ```This improves syntax highlighting and adheres to markdown best practices.
concept/docs/papers/framework/be-framework-whitepaper.md (5)
57-58: Add language specifier to code block.Specify
phpfor the code block to enable syntax highlighting:- ``` + ```php Traditional Middleware:
261-262: Add language specifier to code block.Specify language for ASCII diagram. If this is not executable code, consider using plain text or fenced code without language:
- ``` + ```text ↗ B ↘
783-784: Add language specifier to code block.Specify
textfor the timeline diagram:- ``` + ```text 1950s: The Birth of Instructions (Imperative)
816-823: Format bare URLs in references section as markdown links.References at lines 818-819 have bare URLs. Wrap them in markdown link format for consistency:
## References 1. Ray.Di Dependency Injection Framework. https://github.com/ray-di/Ray.Di - 2. BEAR.Sunday Resource Oriented Framework. https://github.com/bearsunday/BEAR.Sunday + 2. BEAR.Sunday Resource Oriented Framework. [https://github.com/bearsunday/BEAR.Sunday](https://github.com/bearsunday/BEAR.Sunday)Also update the BEAR.Sunday reference to use hyphenation per English conventions if needed, or verify the official repository name.
1-10: Comprehensive whitepaper with strong philosophical content.This is an excellent, well-researched whitepaper that effectively communicates Be Framework's metamorphic programming paradigm. The document successfully bridges technical architecture with philosophical foundations. The examples are clear and the progression from theory to practical implementation is logical.
Noted strengths:
- Unified metaphor of "light through prism" effectively illustrates transformation
- Constructor Workshop Theory clearly articulates the framework's approach
- Real-world examples (dashboard, registration flow) make concepts concrete
- Type-driven metamorphosis sections are particularly well-explained
Minor formatting suggestions above. Overall, approve with optional refinements.
concept/docs/papers/philosophy/dialogue-birth-of-paradigm.md (3)
22-26: Add language specifier to code block.Specify
phpfor syntax highlighting:- ``` + ```php #[Be(ProcessedOrder::class)] // This is a hyperlink! - ``` + ```
32-36: Add language specifier to code block.Specify
phpfor syntax highlighting:- ``` + ```php // First input screen new InputForm() // Blank slate - ``` + ```
1-10: Philosophically rich dialogue effectively communicates Be Framework's ontological foundations.This creative dialogue structure successfully conveys how technical insight (hypermedia) can lead to profound philosophical understanding (irreversible time, cosmic transformation). The progression through eight acts demonstrates a natural evolution of realization. The quantum mechanics parallel (Act VII) adds compelling depth.
Strengths:
- Dialogue format makes abstract concepts accessible
- Transitions between technical and philosophical discourse flow naturally
- Code examples effectively illustrate concepts
- Ending with "EnlightenmentException" is a creative touch that reinforces the themes
Minor formatting suggestions above. The philosophical content is sound and contributes meaningfully to the framework's conceptual narrative.
concept/docs/papers/framework/architecture-as-documentation.md (1)
8-9: Convert emphasis to proper Markdown headings.Lines 9 and 252 use bold emphasis (
**...**) where proper Markdown headings would be more semantically correct:-## Beyond Code as Documentation +## Beyond Code as Documentation -> "The code is the documentation." — Martin Fowler -> "The architecture **is** the documentation." — Be Framework +> "The code is the documentation." — Martin Fowler +> "The architecture is the documentation." — Be Framework -### Architecture as Documentation +### Architecture as Documentation ```phpAnd at line 252:
-### IDE Integration -```typescript -// VS Code extension -be.framework.generateArchitecture({Also applies to: 251-252
concept/docs/papers/patterns/schemalogger-ontological-evolution.md (1)
270-272: Avoid repetitive sentence beginnings.Three successive sentences begin with "Every," creating unintended repetition. Restructure for variety.
-Every execution tells a story. Every story suggests new chapters. Every object contains multitudes. +Each execution tells a story; each suggests new chapters. Objects contain multitudes waiting to unfold.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (2)
concept/docs/study/podcast/be-podcast-vol1.mp3is excluded by!**/*.mp3concept/docs/study/podcast/be-podcast-vol2.mp3is excluded by!**/*.mp3
📒 Files selected for processing (63)
_includes/manuals/1.0/ja/contents.html(1 hunks)concept/dev-docs/HISTORICAL_NOTE.md(1 hunks)concept/dev-docs/PR_DESCRIPTION.md(1 hunks)concept/dev-docs/becoming-architecture-refactor.md(1 hunks)concept/dev-docs/philosophical-heritage.md(1 hunks)concept/dev-docs/psalm-immutability-experiment.md(1 hunks)concept/dev-docs/refactoring-insights.md(1 hunks)concept/dev-docs/todo.md(1 hunks)concept/docs/README-ja.md(1 hunks)concept/docs/README.md(1 hunks)concept/docs/faq/faq-dialogue-with-architect.md(1 hunks)concept/docs/faq/faq-semantic-variable-names.md(1 hunks)concept/docs/manual/00-overview.md(1 hunks)concept/docs/manual/01-input-classes.md(1 hunks)concept/docs/manual/02-being-classes.md(1 hunks)concept/docs/manual/03-final-objects.md(1 hunks)concept/docs/manual/04-metamorphosis-patterns.md(1 hunks)concept/docs/manual/05-philosophy-behind.md(1 hunks)concept/docs/manual/99-from-doing-to-being-final.md(1 hunks)concept/docs/manual/convention/naming-standards.md(1 hunks)concept/docs/manual/index.md(1 hunks)concept/docs/papers/README.md(1 hunks)concept/docs/papers/framework/architecture-as-documentation.md(1 hunks)concept/docs/papers/framework/be-framework-whitepaper.md(1 hunks)concept/docs/papers/framework/being-paradigm-structure.md(1 hunks)concept/docs/papers/framework/terminology.md(1 hunks)concept/docs/papers/integration/alps-be-bidirectional-generation.md(1 hunks)concept/docs/papers/integration/wysiwd-be-framework-convergence.md(1 hunks)concept/docs/papers/patterns/accept-pattern-ontological-delegation.md(1 hunks)concept/docs/papers/patterns/augmented-decision-making.md(1 hunks)concept/docs/papers/patterns/metamorphosis-architecture-manifesto.md(1 hunks)concept/docs/papers/patterns/schemalogger-ontological-evolution.md(1 hunks)concept/docs/papers/patterns/unix-pipes-vs-be-framework.md(1 hunks)concept/docs/papers/philosophy/being-paradigm-when-object-gets-its-becoming.md(1 hunks)concept/docs/papers/philosophy/butterfly-dreams-of-code.md(1 hunks)concept/docs/papers/philosophy/dialogue-birth-of-paradigm.md(1 hunks)concept/docs/papers/philosophy/from-space-to-time.md(1 hunks)concept/docs/papers/philosophy/metamorphose-vs-dci.md(1 hunks)concept/docs/papers/philosophy/noesis-and-noema-when-code-awakes.md(1 hunks)concept/docs/papers/philosophy/ontological-programming-paper.md(1 hunks)concept/docs/papers/philosophy/outlook-is-gold-programming-paradigms-as-world-understanding.md(1 hunks)concept/docs/papers/philosophy/strange-loops-in-code.md(1 hunks)concept/docs/papers/philosophy/temporal-programming-revolution.md(1 hunks)concept/docs/papers/philosophy/ultimate-transparency-article.md(1 hunks)concept/docs/papers/philosophy/when-tests-become-example.md(1 hunks)concept/docs/papers/philosophy/wu-wei-software-design.md(1 hunks)concept/docs/reference/README.md(1 hunks)concept/docs/reference/influences.md(1 hunks)concept/docs/reference/quotes.md(1 hunks)concept/docs/reference/sources.md(1 hunks)concept/docs/reviewer-guide/ai-models.md(1 hunks)concept/docs/reviewer-guide/ai.md(1 hunks)concept/docs/reviewer-guide/human-ja.md(1 hunks)concept/docs/reviewer-guide/human.md(1 hunks)concept/docs/study/README-ja.md(1 hunks)concept/docs/study/README.md(1 hunks)concept/docs/study/merge.sh(1 hunks)concept/docs/study/podcast/README.md(1 hunks)manuals/1.0/ja/01-overview.md(4 hunks)manuals/1.0/ja/03-being-classes.md(2 hunks)manuals/1.0/ja/04-final-objects.md(1 hunks)manuals/1.0/ja/07-type-driven-metamorphosis.md(1 hunks)manuals/1.0/ja/13-vision-ldd.md(1 hunks)
✅ Files skipped from review due to trivial changes (14)
- concept/docs/manual/03-final-objects.md
- concept/docs/reference/sources.md
- concept/docs/faq/faq-dialogue-with-architect.md
- manuals/1.0/ja/04-final-objects.md
- concept/dev-docs/becoming-architecture-refactor.md
- concept/dev-docs/refactoring-insights.md
- concept/docs/manual/99-from-doing-to-being-final.md
- concept/docs/manual/02-being-classes.md
- concept/docs/papers/integration/alps-be-bidirectional-generation.md
- concept/docs/papers/philosophy/outlook-is-gold-programming-paradigms-as-world-understanding.md
- concept/docs/papers/framework/terminology.md
- concept/docs/study/podcast/README.md
- concept/docs/reference/README.md
- concept/docs/papers/integration/wysiwd-be-framework-convergence.md
🧰 Additional context used
📓 Path-based instructions (2)
manuals/1.0/@(en|ja)/**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
manuals/1.0/@(en|ja)/**/*.md: Place new manual pages as Markdown under manuals/1.0/en/ or manuals/1.0/ja/
Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Use .html permalinks for cross-links in content (avoid linking to .md)
Files:
manuals/1.0/ja/07-type-driven-metamorphosis.mdmanuals/1.0/ja/03-being-classes.mdmanuals/1.0/ja/01-overview.mdmanuals/1.0/ja/13-vision-ldd.md
_includes/manuals/1.0/@(en|ja)/contents.html
📄 CodeRabbit inference engine (CLAUDE.md)
Update navigation contents when adding pages (edit _includes/manuals/1.0/[lang]/contents.html)
Files:
_includes/manuals/1.0/ja/contents.html
🧠 Learnings (6)
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Place new manual pages as Markdown under manuals/1.0/en/ or manuals/1.0/ja/
Applied to files:
concept/docs/manual/index.md_includes/manuals/1.0/ja/contents.html
📚 Learning: 2025-09-12T08:33:39.457Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:33:39.457Z
Learning: Be Frameworkの意味変数（VNBDL）は、日本古来の言霊（ことだま）思想と本質的類似性を持つ。言霊では「言葉に霊的な力が宿り現実に影響を及ぼす」が、意味変数では「名前に制約の力が宿り、現れただけで意味と制約が有効になる」。これにより単なる技術手法を超えた日本発の哲学的ソフトウェアパラダイムとして位置づけられる。
Applied to files:
manuals/1.0/ja/07-type-driven-metamorphosis.mdmanuals/1.0/ja/03-being-classes.mdmanuals/1.0/ja/01-overview.mdmanuals/1.0/ja/13-vision-ldd.md
📚 Learning: 2025-09-12T08:21:12.233Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:21:12.233Z
Learning: Be Frameworkの意味変数アプローチは "Variable Name as a Business Domain Language (VNBDL)" と呼ばれ、Martin FowlerのCode As Documentationコンセプトの進化形として位置づけられている。変数名自体をビジネスドメイン言語の語彙とし、型システムレベルでドメインナレッジを実装する革新的なパラダイム。
Applied to files:
manuals/1.0/ja/07-type-driven-metamorphosis.mdmanuals/1.0/ja/01-overview.mdmanuals/1.0/ja/13-vision-ldd.md
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to _includes/manuals/1.0/@(en|ja)/contents.html : Update navigation contents when adding pages (edit _includes/manuals/1.0/[lang]/contents.html)
Applied to files:
_includes/manuals/1.0/ja/contents.html
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Applied to files:
_includes/manuals/1.0/ja/contents.htmlconcept/docs/README-ja.mdmanuals/1.0/ja/13-vision-ldd.md
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Use .html permalinks for cross-links in content (avoid linking to .md)
Applied to files:
_includes/manuals/1.0/ja/contents.html
🪛 LanguageTool
concept/docs/study/README.md
[style] ~66-~66: Consider a different adjective to strengthen your wording.
Context: ...ty**: Paths to innovative discovery and deep understanding open up - **Without intel...
(DEEP_PROFOUND)
[style] ~76-~76: Consider a different adjective to strengthen your wording.
Context: ...y like Gemini 2.5 Pro. This enables deeper understanding while maintaining coheren...
(DEEP_PROFOUND)
[style] ~86-~86: Consider using a different adverb to strengthen your wording.
Context: ...bsolute Beginners Start here if you're completely new to Be Framework and feeling overwhe...
(COMPLETELY_ENTIRELY)
[grammar] ~146-~146: Ensure spelling is correct
Context: ...ile maintaining type safety?" - "How do Been objects carry their own 'proof of work'...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
concept/docs/papers/philosophy/when-tests-become-example.md
[grammar] ~65-~65: Ensure spelling is correct
Context: ...e it has occurred. ## The Discovery of Been The power of this approach becomes appar...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~161-~161: Consider a different adjective to strengthen your wording.
Context: ...hy, and evidence—AI systems can achieve deep understanding of application behavior w...
(DEEP_PROFOUND)
[style] ~191-~191: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... Trust your SQL engine? Trust your ORM? Trust your network layer? These boundaries ar...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~203-~203: Consider a different adjective to strengthen your wording.
Context: ...is transformation reveals programming's deeper relationship to time itself. We are not...
(DEEP_PROFOUND)
concept/dev-docs/PR_DESCRIPTION.md
[style] ~83-~83: The double modal “requires updated” is nonstandard (only accepted in certain dialects). Consider “to be updated”.
Context: ...ing Changes - New architecture requires updated usage patterns - Method signatures chan...
(NEEDS_FIXED)
concept/docs/papers/patterns/accept-pattern-ontological-delegation.md
[style] ~356-~356: This phrase is redundant. Consider writing “evolve”.
Context: ...xisting objects - Decision criteria can evolve over time - Multiple experts can collaborate on c...
(EVOLVE_OVER_TIME)
concept/docs/papers/philosophy/ontological-programming-paper.md
[style] ~49-~49: Consider a different adjective to strengthen your wording.
Context: ...or not by replacing it, but by asking a deeper question. Now, we stand at the threshol...
(DEEP_PROFOUND)
[style] ~597-~597: Consider a different adjective to strengthen your wording.
Context: ...r who they are. Each stage represents a deeper understanding of the nature of computat...
(DEEP_PROFOUND)
manuals/1.0/ja/03-being-classes.md
[uncategorized] ~18-~18: 誤変換です。"自信"の間違いです。
Context: ... ## 内在と超越 存在クラスは変容が実際に起こる場所です。 オブジェクト自身が持つ性質（内在的性質（イマナンス））と、外部から提供される力（超越的な力（トランセン...
(JISINN)
concept/docs/papers/philosophy/dialogue-birth-of-paradigm.md
[style] ~31-~31: Consider a different adjective to strengthen your wording.
Context: ...nted programming!" --- ## Act II: The Deeper Question Human: "What are the diff...
(DEEP_PROFOUND)
[style] ~87-~87: Using many exclamation marks might seem excessive (in this case: 10 exclamation marks for a text that’s 5318 characters long)
Context: ..."This moment of realization is beautiful! Be Framework brings existential time i...
(EN_EXCESSIVE_EXCLAMATION)
[style] ~149-~149: Consider an alternative for the overused word “exactly”.
Context: ...ly Success|Failure $being; ``` This is exactly a quantum state: - Before observation: ...
(EXACTLY_PRECISELY)
concept/docs/papers/patterns/augmented-decision-making.md
[grammar] ~217-~217: Use a hyphen to join words.
Context: ...han painful. This is augmented decision making not just in execution, but in arc...
(QB_NEW_EN_HYPHEN)
[grammar] ~243-~243: Use a hyphen to join words.
Context: ...igence In the era of augmented decision making, our software must be sophisticat...
(QB_NEW_EN_HYPHEN)
[grammar] ~249-~249: Use a hyphen to join words.
Context: .... This is the era of augmented decision making, where our code must be as dynami...
(QB_NEW_EN_HYPHEN)
concept/docs/papers/philosophy/ultimate-transparency-article.md
[style] ~48-~48: Consider using a different verb to strengthen your wording.
Context: ...ut "why it happened." This completeness gives logs sufficient information to serve as...
(GIVE_INFORMATION)
[grammar] ~95-~95: Ensure spelling is correct
Context: ...en extracted from this story: customer, loanApplication, creditScore, approval. These automatic...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
concept/docs/reference/influences.md
[style] ~130-~130: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...opes and channels where water naturally wants to flow. ```php // Creating the landscape...
(REP_WANT_TO_VB)
[uncategorized] ~147-~147: Do not mix variants of the same word (‘dreamed’ and ‘dreamt’) within a single text.
Context: ... The Core Paradox - Am I (Zhuangzi) who dreamed of being a butterfly? - Or am I a butte...
(EN_EXACT_COHERENCY_RULE)
[uncategorized] ~149-~149: Do not mix variants of the same word (‘dreamed’ and ‘dreamt’) within a single text.
Context: ...ere is the boundary between dreamer and dreamed? ##### Profound Implications for Be Fr...
(EN_EXACT_COHERENCY_RULE)
[style] ~192-~192: To elevate your writing, try using an alternative expression here.
Context: ...hey ARE transformation. ##### Why This Matters for Programming - Traditional OOP:...
(MATTERS_RELEVANT)
[style] ~377-~377: The double modal “requires Input” is nonstandard (only accepted in certain dialects). Consider “to be Input”.
Context: ...endent Objects**: Every object requires Input/Inject conditions 2. **Conditional Aris...
(NEEDS_FIXED)
[style] ~580-~580: This phrase is redundant. Consider writing “space”.
Context: ...at gives music its rhythm. Ma is not empty space - it's loaded space, **potential ...
(EMPTY_HOLE)
[style] ~582-~582: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ntial space**, sacred space. ##### Ma in Programming: The Space Between Const...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~1062-~1062: Consider an alternative for the overused word “exactly”.
Context: ...(grasps/feels) other occasions. This is exactly how Be Framework constructors work: **...
(EXACTLY_PRECISELY)
[style] ~1156-~1156: Consider an alternative for the overused word “exactly”.
Context: ...termination of what it becomes. This is exactly what happens in Be Framework constructo...
(EXACTLY_PRECISELY)
concept/dev-docs/philosophical-heritage.md
[style] ~149-~149: This phrase is redundant. Consider writing “moments” or “times”.
Context: ...orality** - Not data containers, but moments in time ## Legacy The Becoming class stands a...
(MOMENT_IN_TIME)
concept/docs/README-ja.md
[uncategorized] ~5-~5: 「ことができる」という表現は冗長な可能性があります。
Context: ...頼性が高く、理解しやすく、正しいソフトウェアを構築するための完全な哲学を見つけることができます。 ## 読書ガイド：どこから始めるか 各文書は前の概念を基に構築されて...
(DOUSI_KOTOGADEKIRU)
concept/docs/README.md
[grammar] ~67-~67: Ensure spelling is correct
Context: ...xistence in code ### 6. **[Ontological Metamorphose vs. DCI: A Comparative Philosophical Re...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~74-~74: Ensure spelling is correct
Context: ...ssignment (DCI) and internal evolution (Metamorphose). * How meaning fragments vs. interna...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
concept/docs/papers/framework/architecture-as-documentation.md
[style] ~208-~208: ‘lags behind’ might be wordy. Consider a shorter alternative.
Context: ... Problems - Outdated: Documentation lags behind code changes - Incomplete: Partial ...
(EN_WORDINESS_PREMIUM_LAGS_BEHIND)
concept/docs/papers/framework/be-framework-whitepaper.md
[grammar] ~819-~819: Use a hyphen to join words.
Context: ...om/ray-di/Ray.Di 2. BEAR.Sunday Resource Oriented Framework. https://github.com/b...
(QB_NEW_EN_HYPHEN)
concept/docs/papers/patterns/schemalogger-ontological-evolution.md
[style] ~271-~271: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ory. Every story suggests new chapters. Every object contains multitudes. This is th...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
concept/docs/papers/philosophy/being-paradigm-when-object-gets-its-becoming.md
[style] ~107-~107: For conciseness, consider replacing this expression with an adverb.
Context: ...c readonly Success|Failure $being; ``` At this moment, the object holds both futures. It is b...
(AT_THE_MOMENT)
[style] ~198-~198: ‘in harmony with’ might be wordy. Consider a shorter alternative.
Context: ...it means: - Natural Action: Acting in harmony with the inherent nature of things - **Effor...
(EN_WORDINESS_PREMIUM_IN_HARMONY_WITH)
[style] ~305-~305: Consider a different adjective to strengthen your wording.
Context: ...ystems than runtime decisions #### The Deep Wisdom The convergence of "Be, Don't D...
(DEEP_PROFOUND)
[style] ~359-~359: ‘in harmony with’ might be wordy. Consider a shorter alternative.
Context: ...t business logic. But now we write them in harmony with the fundamental principle of change. W...
(EN_WORDINESS_PREMIUM_IN_HARMONY_WITH)
[style] ~468-~468: Consider using “incomplete” to avoid wordiness.
Context: .... Like the paradigm it describes, it is not complete but completing, not perfect but perfect...
(NOT_ABLE_PREMIUM)
concept/docs/papers/philosophy/metamorphose-vs-dci.md
[grammar] ~1-~1: Ensure spelling is correct
Context: # Ontological Metamorphose vs. DCI: A Comparative Philosophical Re...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~91-~91: Ensure spelling is correct
Context: ... "living" answer: roles for facets. - Metamorphose: Internal growth—powers transient, re...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
concept/docs/papers/philosophy/wu-wei-software-design.md
[grammar] ~633-~633: Ensure spelling is correct
Context: ...a presence. Not emptiness but fullness; nor chaos, but the deepest possible order. ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
concept/docs/study/README-ja.md
[uncategorized] ~76-~76: 「ことができる」という表現は冗長な可能性があります。
Context: ...。これにより、哲学的基盤から技術的実装まで、全体の一貫性を保ちながら理解を深めることができます。 --- ## 完全なドキュメント読了後のAI向け推奨質問 上記の知...
(DOUSI_KOTOGADEKIRU)
🪛 markdownlint-cli2 (0.18.1)
concept/dev-docs/psalm-immutability-experiment.md
26-26: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
34-34: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
42-42: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
54-54: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
concept/docs/study/README.md
34-34: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
179-179: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
184-184: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
189-189: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
concept/dev-docs/PR_DESCRIPTION.md
94-94: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
manuals/1.0/ja/07-type-driven-metamorphosis.md
120-120: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
122-122: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
concept/docs/papers/patterns/accept-pattern-ontological-delegation.md
141-141: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
concept/docs/reviewer-guide/human-ja.md
103-103: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
concept/docs/reference/quotes.md
99-99: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
concept/docs/papers/philosophy/dialogue-birth-of-paradigm.md
22-22: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
32-32: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
concept/docs/manual/convention/naming-standards.md
9-9: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
252-252: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
concept/docs/papers/philosophy/from-space-to-time.md
2-2: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
25-25: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
concept/docs/papers/philosophy/ultimate-transparency-article.md
101-101: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
concept/docs/papers/philosophy/butterfly-dreams-of-code.md
22-22: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
32-32: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
concept/docs/papers/patterns/metamorphosis-architecture-manifesto.md
277-277: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
manuals/1.0/ja/01-overview.md
18-18: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
28-28: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
29-29: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
30-30: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
concept/docs/reference/influences.md
99-99: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
concept/dev-docs/HISTORICAL_NOTE.md
25-25: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
42-42: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
concept/dev-docs/todo.md
23-23: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
concept/docs/README-ja.md
18-18: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
19-19: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
20-20: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
21-21: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
30-30: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
31-31: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
32-32: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
33-33: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
64-64: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
65-65: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
66-66: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
75-75: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
76-76: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
77-77: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
78-78: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
87-87: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
88-88: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
89-89: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
98-98: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
99-99: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
100-100: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
109-109: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2
(MD005, list-indent)
109-109: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
110-110: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2
(MD005, list-indent)
110-110: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
111-111: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2
(MD005, list-indent)
111-111: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
112-112: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2
(MD005, list-indent)
112-112: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
121-121: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2
(MD005, list-indent)
121-121: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
122-122: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2
(MD005, list-indent)
122-122: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
123-123: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2
(MD005, list-indent)
123-123: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
124-124: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2
(MD005, list-indent)
124-124: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
125-125: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2
(MD005, list-indent)
125-125: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
134-134: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2
(MD005, list-indent)
134-134: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
135-135: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2
(MD005, list-indent)
135-135: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
136-136: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2
(MD005, list-indent)
136-136: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
137-137: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2
(MD005, list-indent)
137-137: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
138-138: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2
(MD005, list-indent)
138-138: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
147-147: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
148-148: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
149-149: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
150-150: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
151-151: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
158-158: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
159-159: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
160-160: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
163-163: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
164-164: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
167-167: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
168-168: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
171-171: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
172-172: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
175-175: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
176-176: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
177-177: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
182-182: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
183-183: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
184-184: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
187-187: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
188-188: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
189-189: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
194-194: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
195-195: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
196-196: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
199-199: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
200-200: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
201-201: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
204-204: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
205-205: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
206-206: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
211-211: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
212-212: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
213-213: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
216-216: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
217-217: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
218-218: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
221-221: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
222-222: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
223-223: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
concept/docs/papers/framework/architecture-as-documentation.md
9-9: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
252-252: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
concept/docs/papers/framework/be-framework-whitepaper.md
10-10: Blank line inside blockquote
(MD028, no-blanks-blockquote)
57-57: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
261-261: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
783-783: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
818-818: Bare URL used
(MD034, no-bare-urls)
819-819: Bare URL used
(MD034, no-bare-urls)
828-828: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
concept/docs/papers/framework/being-paradigm-structure.md
49-49: Heading levels should only increment by one level at a time
Expected: h2; Actual: h4
(MD001, heading-increment)
concept/docs/papers/philosophy/being-paradigm-when-object-gets-its-becoming.md
22-22: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
32-32: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
concept/docs/papers/philosophy/strange-loops-in-code.md
163-163: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
593-593: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
concept/docs/reviewer-guide/ai.md
24-24: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
29-29: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
33-33: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
38-38: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
manuals/1.0/ja/13-vision-ldd.md
16-16: Blank line inside blockquote
(MD028, no-blanks-blockquote)
🪛 Shellcheck (0.11.0)
concept/docs/study/merge.sh
[warning] 14-14: This redirection doesn't have a command. Move to its command (or use 'true' as no-op).
(SC2188)
There was a problem hiding this comment.
Actionable comments posted: 9
🧹 Nitpick comments (4)
concept/dev-docs/HISTORICAL_NOTE.md (1)
42-42: Optional: Consider converting the epigraph to a proper heading or comment format.Line 42 uses emphasis (
*...*) for a philosophical quote, which triggers theMD036linting rule. While this is a stylistic choice and italics are semantically appropriate for an epigraph, you may prefer to either:
- Upgrade to a comment:
<!-- "The path to ontological programming..." -->- Use a blockquote:
> "The path to ontological programming..."- Leave as-is if intentional emphasis is desired
This is a minor style preference and not a functional issue.
concept/docs/study/README.md (1)
193-198: Add bash language specifiers to markdown code blocks.Lines 193 and 198 contain bash command examples in code fences but lack the language identifier. Per markdown best practices (MD040), add
bashto the code fence opening.Apply this diff to fix the code fence language specifiers:
-### Clean up split files -``` +### Clean up split files +```bash # Remove the split files after use rm merged_[0-9][0-9].txt -``` +```Also fix line 193:
-2. Upload subsequent parts (`merged_01.txt`, `merged_02.txt`, etc.) with: - ``` +2. Upload subsequent parts (`merged_01.txt`, `merged_02.txt`, etc.) with: + ```bash This is part 2/3/4... of the Be Framework documentation. Please read and understand this part, but don't respond yet. More parts to follow. - ``` + ```Note: The second instance (line 193) contains plain text instructions rather than executable bash, so you may alternatively use
textinstead ofbashfor that fence if preferred.concept/dev-docs/psalm-immutability-experiment.md (1)
234-240: Conclusion adequately summarizes findings.The "Key Insight" and "Recommendation" clearly restate the core takeaway. Minor note: Lines 221 and 217 already cover recommendations, so the "Recommendation" paragraph (line 240) is somewhat redundant with the "Future Recommendations" section, though it effectively encapsulates the essence.
concept/docs/papers/framework/be-framework-whitepaper.md (1)
828-828: Move epilogue text from emphasis to blockquote or prose.Line 828 uses emphasis (
*...*) to frame a reflective statement. Given the contemplative nature of this epilogue, consider a blockquote or plain prose instead.-*"Just as an individual transforms by accepting their unchangeable circumstances and using their skills to become a new, better self, each object in Be Framework does the same. This framework reflects our own journey of growth and transformation."* +> Just as an individual transforms by accepting their unchangeable circumstances and using their skills to become a new, better self, each object in Be Framework does the same. This framework reflects our own journey of growth and transformation.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (21)
CLAUDE.md(1 hunks)concept/dev-docs/HISTORICAL_NOTE.md(1 hunks)concept/dev-docs/PR_DESCRIPTION.md(1 hunks)concept/dev-docs/psalm-immutability-experiment.md(1 hunks)concept/docs/manual/99-from-doing-to-being-final.md(1 hunks)concept/docs/papers/framework/architecture-as-documentation.md(1 hunks)concept/docs/papers/framework/be-framework-whitepaper.md(1 hunks)concept/docs/papers/integration/wysiwd-be-framework-convergence.md(1 hunks)concept/docs/papers/patterns/augmented-decision-making.md(1 hunks)concept/docs/papers/philosophy/butterfly-dreams-of-code.md(1 hunks)concept/docs/papers/philosophy/from-space-to-time.md(1 hunks)concept/docs/papers/philosophy/ontological-programming-paper.md(1 hunks)concept/docs/papers/philosophy/strange-loops-in-code.md(1 hunks)concept/docs/papers/philosophy/ultimate-transparency-article.md(1 hunks)concept/docs/papers/philosophy/wu-wei-software-design.md(1 hunks)concept/docs/study/README-ja.md(1 hunks)concept/docs/study/README.md(1 hunks)manuals/1.0/en/00-overview.md(1 hunks)manuals/1.0/en/01-overview.md(2 hunks)manuals/1.0/ja/01-overview.md(4 hunks)manuals/1.0/ja/convention/naming-standards.md(2 hunks)
✅ Files skipped from review due to trivial changes (1)
- CLAUDE.md
🚧 Files skipped from review as they are similar to previous changes (3)
- concept/docs/papers/philosophy/strange-loops-in-code.md
- concept/docs/manual/99-from-doing-to-being-final.md
- concept/dev-docs/PR_DESCRIPTION.md
🧰 Additional context used
📓 Path-based instructions (1)
manuals/1.0/@(en|ja)/**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
manuals/1.0/@(en|ja)/**/*.md: Place new manual pages as Markdown under manuals/1.0/en/ or manuals/1.0/ja/
Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Use .html permalinks for cross-links in content (avoid linking to .md)
Files:
manuals/1.0/ja/convention/naming-standards.mdmanuals/1.0/en/00-overview.mdmanuals/1.0/ja/01-overview.mdmanuals/1.0/en/01-overview.md
🧠 Learnings (4)
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Applied to files:
manuals/1.0/ja/convention/naming-standards.mdmanuals/1.0/en/00-overview.md
📚 Learning: 2025-09-12T08:33:39.457Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:33:39.457Z
Learning: Be Frameworkの意味変数（VNBDL）は、日本古来の言霊（ことだま）思想と本質的類似性を持つ。言霊では「言葉に霊的な力が宿り現実に影響を及ぼす」が、意味変数では「名前に制約の力が宿り、現れただけで意味と制約が有効になる」。これにより単なる技術手法を超えた日本発の哲学的ソフトウェアパラダイムとして位置づけられる。
Applied to files:
manuals/1.0/ja/01-overview.md
📚 Learning: 2025-09-12T08:21:12.233Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:21:12.233Z
Learning: Be Frameworkの意味変数アプローチは "Variable Name as a Business Domain Language (VNBDL)" と呼ばれ、Martin FowlerのCode As Documentationコンセプトの進化形として位置づけられている。変数名自体をビジネスドメイン言語の語彙とし、型システムレベルでドメインナレッジを実装する革新的なパラダイム。
Applied to files:
manuals/1.0/ja/01-overview.md
📚 Learning: 2025-12-16T11:23:39.048Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 10
File: concept/dev-docs/PR_DESCRIPTION.md:94-94
Timestamp: 2025-12-16T11:23:39.048Z
Learning: In this repository, fenced code blocks without language identifiers are acceptable and should not be flagged during review.
Applied to files:
concept/docs/papers/philosophy/butterfly-dreams-of-code.md
🪛 LanguageTool
concept/docs/study/README-ja.md
[uncategorized] ~76-~76: 「ことができる」という表現は冗長な可能性があります。
Context: ...。これにより、哲学的基盤から技術的実装まで、全体の一貫性を保ちながら理解を深めることができます。 --- ## 完全なドキュメント読了後のAI向け推奨質問 上記の知...
(DOUSI_KOTOGADEKIRU)
concept/docs/papers/framework/architecture-as-documentation.md
[style] ~208-~208: ‘lags behind’ might be wordy. Consider a shorter alternative.
Context: ... Problems - Outdated: Documentation lags behind code changes - Incomplete: Partial ...
(EN_WORDINESS_PREMIUM_LAGS_BEHIND)
manuals/1.0/en/01-overview.md
[style] ~11-~11: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...objects to transform into the self they want to be, by their own will. Marcel Proust s...
(REP_WANT_TO_VB)
[style] ~16-~16: ‘In Search of’ might be wordy. Consider a shorter alternative.
Context: ...es. > > —Marcel Proust, 'The Prisoner' (In Search of Lost Time, Volume 5) 1923 ## Why Not a...
(EN_WORDINESS_PREMIUM_IN_SEARCH_OF)
[style] ~25-~25: Consider using a different adverb to strengthen your wording.
Context: ... system by itself. Be Framework adopts a completely different approach, incorporating the p...
(COMPLETELY_ENTIRELY)
[grammar] ~25-~25: Ensure spelling is correct
Context: ...ere one abandons artifice (control) and entrusts things to proceed to their natural stat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
concept/docs/papers/philosophy/ultimate-transparency-article.md
[style] ~48-~48: Consider using a different verb to strengthen your wording.
Context: ...ut "why it happened." This completeness gives logs sufficient information to serve as...
(GIVE_INFORMATION)
[grammar] ~95-~95: Ensure spelling is correct
Context: ...en extracted from this story: customer, loanApplication, creditScore, approval. These automatic...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
concept/docs/study/README.md
[style] ~66-~66: Consider a different adjective to strengthen your wording.
Context: ...ty**: Paths to innovative discovery and deep understanding open up - **Without intel...
(DEEP_PROFOUND)
[style] ~76-~76: Consider a different adjective to strengthen your wording.
Context: ...y like Gemini 2.5 Pro. This enables deeper understanding while maintaining coheren...
(DEEP_PROFOUND)
[style] ~86-~86: Consider using a different adverb to strengthen your wording.
Context: ...bsolute Beginners Start here if you're completely new to Be Framework and feeling overwhe...
(COMPLETELY_ENTIRELY)
[grammar] ~146-~146: Ensure spelling is correct
Context: ...ile maintaining type safety?" - "How do Been objects carry their own 'proof of work'...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
concept/docs/papers/patterns/augmented-decision-making.md
[grammar] ~217-~217: Use a hyphen to join words.
Context: ...han painful. This is augmented decision making not just in execution, but in arc...
(QB_NEW_EN_HYPHEN)
[grammar] ~243-~243: Use a hyphen to join words.
Context: ...igence In the era of augmented decision making, our software must be sophisticat...
(QB_NEW_EN_HYPHEN)
[grammar] ~249-~249: Use a hyphen to join words.
Context: .... This is the era of augmented decision making, where our code must be as dynami...
(QB_NEW_EN_HYPHEN)
concept/docs/papers/framework/be-framework-whitepaper.md
[grammar] ~819-~819: Use a hyphen to join words.
Context: ...om/ray-di/Ray.Di 2. BEAR.Sunday Resource Oriented Framework. https://github.com/b...
(QB_NEW_EN_HYPHEN)
concept/docs/papers/philosophy/ontological-programming-paper.md
[style] ~49-~49: Consider a different adjective to strengthen your wording.
Context: ...or not by replacing it, but by asking a deeper question. Now, we stand at the threshol...
(DEEP_PROFOUND)
[style] ~597-~597: Consider a different adjective to strengthen your wording.
Context: ...r who they are. Each stage represents a deeper understanding of the nature of computat...
(DEEP_PROFOUND)
concept/docs/papers/philosophy/wu-wei-software-design.md
[grammar] ~633-~633: Ensure spelling is correct
Context: ...a presence. Not emptiness but fullness; nor chaos, but the deepest possible order. ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🪛 markdownlint-cli2 (0.18.1)
manuals/1.0/en/01-overview.md
28-28: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
29-29: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
30-30: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
concept/docs/study/README.md
193-193: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
198-198: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
concept/docs/papers/framework/be-framework-whitepaper.md
10-10: Blank line inside blockquote
(MD028, no-blanks-blockquote)
818-818: Bare URL used
(MD034, no-bare-urls)
819-819: Bare URL used
(MD034, no-bare-urls)
828-828: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
concept/dev-docs/HISTORICAL_NOTE.md
42-42: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
concept/docs/papers/philosophy/from-space-to-time.md
143-143: Dollar signs used before commands without showing output
(MD014, commands-show-output)
🔇 Additional comments (26)
concept/dev-docs/HISTORICAL_NOTE.md (1)
1-38: Excellent historical context documentation that aligns well with PR objectives.The document clearly explains the repository's experimental nature, preservation of design decisions, and philosophical journey—all key themes in this PR. The structure is logical, metadata is helpful, and the tone appropriately positions this as an archive while maintaining active development messaging.
concept/docs/papers/patterns/augmented-decision-making.md (1)
1-253: Excellent introduction to augmented decision-making philosophy.The document effectively articulates the Be Framework's approach to decision-making by combining deterministic logic, pattern discovery, and human intuition. The progression from identifying the problem (incomplete information assumptions) through concrete examples (hiring, loan applications) to architectural implications is compelling and well-structured.
The
#[Accept]pattern and the concept of undetermined states as features rather than failures are particularly well explained. The framing of context preservation and semantic validation through directory structure and variable naming creates a clear vision for maintainable, transparent decision architectures.Real-world scenarios ground abstract concepts, and the metrics-of-success section appropriately shifts the conversation from correctness to adaptability. The philosophical conclusion ties the technical patterns back to broader principles about knowledge, intuition, and evolution.
manuals/1.0/ja/convention/naming-standards.md (3)
2-2: Frontmatter and permalink format are correct.The layout is properly specified as
docs-jafor Japanese documentation, and the permalink correctly uses the.htmlformat as required by coding guidelines.Also applies to: 5-5
150-150: Code fence language specifications improve plaintext rendering.The changes from generic
```to```textfor file/directory structure examples are a best practice. This prevents syntax highlighters from incorrectly interpreting directory trees and ensures these sections render as plain text.Also applies to: 162-162
1-200: Clarify scope: this appears to be a consistency refactor rather than a new English translation.The PR objective emphasizes adding English translations, but this file is a modified Japanese manual. The AI summary notes this as "restructured manuals" with minor code fence improvements. If this file modification is intentional as part of consistency improvements across the documentation set (alongside new English translations), that context should be clarified in the PR description or commit messages to avoid confusion about scope.
Can you confirm whether this Japanese manual modification is intended as a consistency/refactoring change across the documentation set, or if there are English translation files that should also be reviewed?
concept/docs/papers/philosophy/butterfly-dreams-of-code.md (1)
1-439: Excellent philosophical treatise—well-structured and ready to publish.This document successfully introduces Log-Driven Development through a compelling philosophical lens, drawing on Zhuangzi, Buddhist Dependent Origination, Daoist Wu Wei, and Process Philosophy. The narrative arc from paradox to acceptance is coherent and engaging. All code blocks have proper language specifiers (PHP, JSON, text), markdown formatting is correct, and the seven references are appropriately cited. The conceptual code examples effectively illustrate the core ideas without requiring literal executability. The epilogue reinforces the koanic nature of the work, aligning perfectly with the PR objective to present these ideas as an invitation to a new way of thinking about code.
concept/docs/papers/philosophy/from-space-to-time.md (5)
1-129: Excellent philosophical foundation and structure.The essay is well-organized with clear progression from spatial to temporal paradigms. The abstract, TOC, and introduction effectively frame the shift from hypertext/Web metaphors to metamorphic programming. Philosophy references (Heidegger, Bergson, Whitehead) are aptly chosen and well-integrated.
135-400: Strong philosophical and practical examples throughout.The four pillars of temporal programming (Irreversibility, Memory Through Being, Existential State, Metamorphic Destiny), supported by PHP code examples using the
#[Be(...)]attribute, effectively illustrate core concepts. Examples using Child→Adult, error handling, and time-aware DI demonstrate practical application while maintaining philosophical coherence.
401-575: Case studies demonstrate real-world patterns.The three case studies (registration flow as life journey, shopping cart as relationship, deployment pipeline as evolution) thoughtfully apply temporal metamorphosis concepts to familiar application domains. The narrative framing (Conception→Birth→Childhood→Maturity for users; First Meeting→Growing Connection→Commitment for carts) makes abstract philosophy concrete without sacrificing depth.
576-947: Maintains philosophical rigor through conclusion.The "Future of Temporal Programming" section, cosmic perspective, and epilogue elegantly close the narrative while staying true to the temporal transformation theme. The meta-observation that the paper itself underwent metamorphosis during writing is a fitting touch that reinforces rather than undermines credibility. Prose quality is consistently high.
953-963: Verify references are accurate and accessible.Seven of eight references are classical philosophical/technical works; one is to Be Framework documentation (2024). Please confirm that all cited works match their listed publication years (Heidegger 1927, Bergson 1889, Whitehead 1929, Nelson 1965, Berners-Lee 1989, Fielding 2000) and that internal framework references (lines 961–962) point to existing or planned documentation.
manuals/1.0/en/00-overview.md (2)
1-6: Frontmatter and file placement are correct.The file is properly placed at
manuals/1.0/en/00-overview.mdwith the required YAML frontmatter includinglayout: docs-enand.htmlpermalink.
83-83: Link format is correct.The cross-reference uses the required
.htmlpermalink format instead of.md.manuals/1.0/en/01-overview.md (2)
107-107: Link format and Jekyll template syntax are correct.The liquid filter
relative_urlcorrectly targets the.htmlpermalink. This Jekyll template approach is appropriate for this file structure.
10-32: Content updates coherently introduce Wu Wei philosophy and state-oriented framing.The added sections (Proust introduction, Wu Wei/Non-doing, Commander-to-Gardener metaphor) effectively establish the philosophical foundation aligned with the PR objective. Phrasing and examples are clear.
manuals/1.0/ja/01-overview.md (3)
1-6: Japanese version frontmatter is correct.The file uses
layout: docs-ja(appropriate for Japanese content) with proper file locationmanuals/1.0/ja/01-overview.mdand.htmlpermalink format.
107-107: Japanese version link format is correct.The Jekyll
relative_urltemplate filter correctly targets the.htmlpermalink.
10-32: Japanese translation maintains conceptual alignment with philosophical framing.The Japanese version properly renders the Wu Wei philosophy (無為自然), Commander-to-Gardener metaphor (司令官/庭師), and state-oriented concepts with culturally appropriate terminology. The translations are coherent and support the PR objective of international communication.
concept/dev-docs/psalm-immutability-experiment.md (3)
92-101: Core pattern example is clear and concrete.The code snippet effectively demonstrates the incompatibility between framework architecture and Psalm's strictness. Good use of comments to annotate which operations Psalm considers "impure."
125-160: Practical value assessment is well-reasoned.The distinction between class-level and method-level annotations is insightful, and the discovery that
@psalm-mutation-freehas higher practical value than@psalm-immutableis a useful conclusion for the team.
217-232: Actionable recommendations are clear.The split between "For Be Framework Development" and "For Framework Design Generally" provides both immediate guidance and broader insights. The specific recommendations (e.g., "Skip
@psalm-immutableClass Annotations," focus onreadonlyclasses) are pragmatic and implementable.concept/docs/papers/framework/be-framework-whitepaper.md (1)
1-825: Excellent whitepaper establishing Metamorphic Programming foundations.This document comprehensively introduces the Metamorphic Programming paradigm through clear metaphors (light through prism, metamorphosis cycles), solid architectural principles (constructor-only processing, type transparency), and practical patterns (linear chains, parallel assembly, type-driven metamorphosis). The progression from theory to real-world examples (dashboard assembly, user registration) effectively demonstrates the paradigm's power. Cross-references to related documentation are well-placed, and the philosophical framing aligns strongly with the PR objectives to present ontological programming as a new way of thinking.
concept/docs/papers/philosophy/wu-wei-software-design.md (1)
1-643: Outstanding integration of Wu Wei philosophy with practical software architecture.This essay brilliantly translates ancient Taoist principles into modern software design, using compelling metaphors (water defeating stone, ecosystems, rivers) and concrete architectural examples (REST, microservices, being-oriented programming). The diagnosis of controller-centric failures (Act 1-3 lifecycle) is incisive, and the proposed flow-based design principles (enable over control, constraints as channels, composition over orchestration) directly address real architectural pain points. The connection to Be Framework's metamorphosis patterns and the programmer-as-gardener role provides practical grounding for abstract philosophical concepts. Excellent addition to the framework philosophy documentation.
concept/docs/papers/framework/architecture-as-documentation.md (1)
1-290: Clear, practical introduction to Architecture as Documentation concept.This document effectively explains how Ontological Programming enables architecture itself to become documentation through structural, semantic, and execution transparency. The three visualization modes for
be-tree(basic structure, semantic analysis, flow visualization) provide clear mental models for understanding system architecture at different levels. The comparison table (line 236-244) effectively contrasts traditional approaches with architecture-as-documentation. Mermaid diagram examples are concrete and helpful. The progression from concept to implementation to future possibilities is logical and well-scoped. Good addition to the framework documentation.concept/docs/papers/philosophy/ontological-programming-paper.md (1)
1-686: Comprehensive and philosophically rigorous foundation for Ontological Programming.This paper establishes Ontological Programming as a fundamental paradigm shift from "doing" to "being," grounded in clear theoretical foundations (five core principles, existence contracts) and demonstrated across multiple programming languages (Python, Java, Haskell, TypeScript, Rust, SQL, CSS). The progression from payment processing systems to philosophical implications effectively shows the paradigm's scope. The type system section clearly explains how types become existence conditions, and the patterns section (existence chains, parallel existence, composite existence, type-driven metamorphosis) provides mental models for designing with the paradigm. The treatment of AI-era programming and the "Whether?" question (lines 13-24) adds timely relevance. Excellent contribution to the framework's theoretical foundation.
concept/docs/papers/philosophy/ultimate-transparency-article.md (1)
1-111: Concise, compelling introduction to transparency, reversibility, and Log-Driven Development.This article effectively introduces three key concepts: the reversibility between code and specification via semantic logs, the Three Transparencies (structural, semantic, execution) that enable it, and Log-Driven Development as a new methodology contrasting with TDD. The formula "Code ⟷ Execution ⟷ Log ⟷ Specification" is simple and powerful. The progression from semantic logs as executable specifications through the new development flow (stories → semantic terms → ALPS → decision graphs → generated code) shows practical application. While brief, the document establishes important vision concepts that align with the PR's introduction of LDD philosophy. Excellent complementary addition to the broader ontological programming documentation.
1f47e57 to
89de5a6
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
manuals/1.0/en/01-overview.md (1)
27-30: Fix markdown list indentation to 2 spaces.Nested list items use 4-space indentation, but Markdown best practice (enforced by markdownlint MD007) requires 2-space indentation for proper nesting. This was flagged in the previous review.
Apply this diff:
* Commander to Gardener: - * The Commander (Controller) orders subordinates (Objects) to "Move!". But it is impossible to keep ordering all complex autonomous movements. - * The Gardener does not order plants. They only prepare the environment like water and light. - * Plants care only about their own transformation. They do not try to change others, but accept the environment and transform themselves autonomously (Metamorphosis) to become what they should be. + * The Commander (Controller) orders subordinates (Objects) to "Move!". But it is impossible to keep ordering all complex autonomous movements. + * The Gardener does not order plants. They only prepare the environment like water and light. + * Plants care only about their own transformation. They do not try to change others, but accept the environment and transform themselves autonomously (Metamorphosis) to become what they should be.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (4)
manuals/1.0/en/00-overview.md(1 hunks)manuals/1.0/en/01-overview.md(2 hunks)manuals/1.0/ja/01-overview.md(4 hunks)manuals/1.0/ja/13-vision-ldd.md(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- manuals/1.0/en/00-overview.md
🧰 Additional context used
📓 Path-based instructions (1)
manuals/1.0/@(en|ja)/**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
manuals/1.0/@(en|ja)/**/*.md: Place new manual pages as Markdown under manuals/1.0/en/ or manuals/1.0/ja/
Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Use .html permalinks for cross-links in content (avoid linking to .md)
Files:
manuals/1.0/ja/01-overview.mdmanuals/1.0/en/01-overview.mdmanuals/1.0/ja/13-vision-ldd.md
🧠 Learnings (4)
📓 Common learnings
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:33:39.457Z
Learning: Be Frameworkの意味変数（VNBDL）は、日本古来の言霊（ことだま）思想と本質的類似性を持つ。言霊では「言葉に霊的な力が宿り現実に影響を及ぼす」が、意味変数では「名前に制約の力が宿り、現れただけで意味と制約が有効になる」。これにより単なる技術手法を超えた日本発の哲学的ソフトウェアパラダイムとして位置づけられる。
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:21:12.233Z
Learning: Be Frameworkの意味変数アプローチは "Variable Name as a Business Domain Language (VNBDL)" と呼ばれ、Martin FowlerのCode As Documentationコンセプトの進化形として位置づけられている。変数名自体をビジネスドメイン言語の語彙とし、型システムレベルでドメインナレッジを実装する革新的なパラダイム。
📚 Learning: 2025-09-12T08:33:39.457Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:33:39.457Z
Learning: Be Frameworkの意味変数（VNBDL）は、日本古来の言霊（ことだま）思想と本質的類似性を持つ。言霊では「言葉に霊的な力が宿り現実に影響を及ぼす」が、意味変数では「名前に制約の力が宿り、現れただけで意味と制約が有効になる」。これにより単なる技術手法を超えた日本発の哲学的ソフトウェアパラダイムとして位置づけられる。
Applied to files:
manuals/1.0/ja/01-overview.mdmanuals/1.0/ja/13-vision-ldd.md
📚 Learning: 2025-09-12T08:21:12.233Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:21:12.233Z
Learning: Be Frameworkの意味変数アプローチは "Variable Name as a Business Domain Language (VNBDL)" と呼ばれ、Martin FowlerのCode As Documentationコンセプトの進化形として位置づけられている。変数名自体をビジネスドメイン言語の語彙とし、型システムレベルでドメインナレッジを実装する革新的なパラダイム。
Applied to files:
manuals/1.0/ja/01-overview.mdmanuals/1.0/ja/13-vision-ldd.md
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Applied to files:
manuals/1.0/ja/13-vision-ldd.md
🪛 LanguageTool
manuals/1.0/en/01-overview.md
[style] ~11-~11: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...objects to transform into the self they want to be, by their own will. Marcel Proust s...
(REP_WANT_TO_VB)
[style] ~16-~16: ‘In Search of’ might be wordy. Consider a shorter alternative.
Context: ...es. > > —Marcel Proust, 'The Prisoner' (In Search of Lost Time, Volume 5) 1923 ## Why Not a...
(EN_WORDINESS_PREMIUM_IN_SEARCH_OF)
[style] ~25-~25: Consider using a different adverb to strengthen your wording.
Context: ... system by itself. Be Framework adopts a completely different approach, incorporating the p...
(COMPLETELY_ENTIRELY)
[grammar] ~25-~25: Ensure spelling is correct
Context: ...ere one abandons artifice (control) and entrusts things to proceed to their natural stat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🪛 markdownlint-cli2 (0.18.1)
manuals/1.0/en/01-overview.md
28-28: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
29-29: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
30-30: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
manuals/1.0/ja/13-vision-ldd.md
28-28: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
29-29: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
30-30: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
🔇 Additional comments (7)
manuals/1.0/ja/01-overview.md (4)
1-6: Frontmatter conforms to documentation guidelines.The layout is correctly set to
docs-jaand the permalink uses the.htmlformat per coding guidelines.
18-32: Wu Wei philosophy is well-articulated with clear Commander-to-Gardener analogy.The introduction of Wu Wei (無為自然) and the shift from control-centric to environment-centric thinking is compelling. The Commander→Gardener metaphor effectively contrasts direct control with autonomous transformation through environmental shaping. This aligns well with the PR objective to introduce Ontological Programming concepts.
34-102: DOING→BEING reframing is clear and well-supported with examples.The section effectively demonstrates how BEING-centric design shifts from imperative action (
$user->delete()) to state representation (DeletedUser). The progression through type-driven validation (ValidatedUser, SavedUser, DeletedUser) and the explanation of why BEING eliminates class validation logic is pedagogically sound and reinforces the framework's philosophy.
107-107: Cross-link uses correct.htmlpermalink format.The relative link to the input classes manual follows the coding guideline requirement to use
.htmlpermalinks instead of.mdreferences.Please confirm that
02-input-classes.htmlis included in this PR or already exists in the repository.manuals/1.0/en/01-overview.md (1)
1-109: Excellent alignment with PR objectives and philosophy.The translated manual successfully introduces Wu Wei, the Commander-to-Gardener metaphor, and the shift from DOING to BEING paradigms. The code examples clearly illustrate the state-centric approach, and the layout/formatting (aside from list indentation) follows coding guidelines correctly.
manuals/1.0/ja/13-vision-ldd.md (2)
1-6: Frontmatter correctly configured.The layout, title, category, and permalink are properly set. The
docs-jalayout and.htmlpermalink follow the required format for Japanese manual pages. As per coding guidelines, this structure is correct.
8-78: Content structure and philosophical framing are coherent and well-executed.The narrative effectively introduces Log-Driven Development through the lens of the Zhuangzi butterfly dream metaphor, establishing conceptual connections between logs, code, and specifications. The three transparency modalities (structural, semantic, execution) are clearly explained with concrete examples (e.g.,
#[Be]attributes,
koriym
changed the title
d0d97fa to
ede9847
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
manuals/1.0/ja/13-vision-ldd.md (1)
8-78: Well-structured LDD documentation with coherent philosophy.The Log-Driven Development content effectively introduces the transparency concepts, the Infinite Loop of Value, and the butterfly dream metaphor. The narrative is philosophically coherent with the broader Be Framework vision.
Optional markdown improvement: The blank line inside the blockquote at Line 16 triggers MD028. You may remove it if you prefer strict markdown compliance, though it doesn't affect rendering:
> —荘子『斉物論』（紀元前4世紀頃） - > **注意**: 本章はBe Frameworkが目指す「未来のビジョン」を記述したものです。現在のバージョンではすべてが実装されているわけではありません。Note: The MD007 list indentation issues flagged by the linter on lines 28, 30, 32 were previously addressed in commit d0d97fa according to past review comments.
manuals/1.0/en/13-vision-ldd.md (1)
8-75: Well-structured English LDD documentation.The Log-Driven Development content effectively communicates the transparency concepts, reversibility, and the Butterfly Dream philosophy. The English translation maintains the philosophical depth of the Japanese original.
Optional markdown improvement: The blank line inside the blockquote at Line 13 triggers MD028. You may remove it for strict markdown compliance:
> —Zhuangzi, 'The Adjustment of Controversies' (Qi Wu Lun) (Circa 4th Century BC) - > **Note**: This chapter describes the "Future Vision" that Be Framework aims for. Not everything is implemented in the current version.manuals/1.0/ja/01-overview.md (1)
34-109: Well-structured overview demonstrating the DOING-to-BEING shift.The examples clearly illustrate the paradigm shift from action-based to state-based programming. The type system examples effectively show how BEING prevents invalid states at compile time.
Optional markdown improvement: The nested list items at lines 28-30 use 4-space indentation. Markdown best practice recommends 2-space indentation for nested lists:
* Commander (司令官) から Gardener (庭師) へ: - * 司令官(Controller)は、部下(オブジェクト)に「動け」と命令します。しかし、複雑な自律的な動きを全て命令し続けることは不可能です。 - * 庭師は、植物に命令しません。ただ、水や光という環境を整えるだけです。 - * 植物は、自らの変容のみに関心を持ちます。他者を変えようとするのではなく、環境を受け入れて自らを自律的に変容(Metamorphosis)させ、在るべき姿に成ります。 + * 司令官(Controller)は、部下(オブジェクト)に「動け」と命令します。しかし、複雑な自律的な動きを全て命令し続けることは不可能です。 + * 庭師は、植物に命令しません。ただ、水や光という環境を整えるだけです。 + * 植物は、自らの変容のみに関心を持ちます。他者を変えようとするのではなく、環境を受け入れて自らを自律的に変容(Metamorphosis)させ、在るべき姿に成ります。
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (15)
.github/workflows/claude-code-review.yml(1 hunks)_includes/manuals/1.0/en/contents.html(1 hunks)_includes/manuals/1.0/ja/contents.html(1 hunks)manuals/1.0/en/00-overview.md(1 hunks)manuals/1.0/en/01-overview.md(2 hunks)manuals/1.0/en/02-input-classes.md(3 hunks)manuals/1.0/en/03-being-classes.md(4 hunks)manuals/1.0/en/04-final-objects.md(4 hunks)manuals/1.0/en/12-philosophy-behind.md(1 hunks)manuals/1.0/en/13-vision-ldd.md(1 hunks)manuals/1.0/ja/01-overview.md(4 hunks)manuals/1.0/ja/03-being-classes.md(2 hunks)manuals/1.0/ja/04-final-objects.md(1 hunks)manuals/1.0/ja/07-type-driven-metamorphosis.md(1 hunks)manuals/1.0/ja/13-vision-ldd.md(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
- .github/workflows/claude-code-review.yml
- manuals/1.0/en/00-overview.md
- _includes/manuals/1.0/ja/contents.html
🧰 Additional context used
📓 Path-based instructions (2)
manuals/1.0/@(en|ja)/**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
manuals/1.0/@(en|ja)/**/*.md: Place new manual pages as Markdown under manuals/1.0/en/ or manuals/1.0/ja/
Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Use .html permalinks for cross-links in content (avoid linking to .md)
Files:
manuals/1.0/ja/04-final-objects.mdmanuals/1.0/ja/13-vision-ldd.mdmanuals/1.0/ja/03-being-classes.mdmanuals/1.0/en/02-input-classes.mdmanuals/1.0/en/12-philosophy-behind.mdmanuals/1.0/en/03-being-classes.mdmanuals/1.0/en/01-overview.mdmanuals/1.0/ja/07-type-driven-metamorphosis.mdmanuals/1.0/en/13-vision-ldd.mdmanuals/1.0/en/04-final-objects.mdmanuals/1.0/ja/01-overview.md
_includes/manuals/1.0/@(en|ja)/contents.html
📄 CodeRabbit inference engine (CLAUDE.md)
Update navigation contents when adding pages (edit _includes/manuals/1.0/[lang]/contents.html)
Files:
_includes/manuals/1.0/en/contents.html
🧠 Learnings (6)
📓 Common learnings
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to _includes/manuals/1.0/@(en|ja)/contents.html : Update navigation contents when adding pages (edit _includes/manuals/1.0/[lang]/contents.html)
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Place new manual pages as Markdown under manuals/1.0/en/ or manuals/1.0/ja/
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to _includes/manuals/1.0/@(en|ja)/contents.html : Update navigation contents when adding pages (edit _includes/manuals/1.0/[lang]/contents.html)
Applied to files:
manuals/1.0/ja/04-final-objects.md_includes/manuals/1.0/en/contents.html
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Applied to files:
manuals/1.0/ja/13-vision-ldd.md_includes/manuals/1.0/en/contents.html
📚 Learning: 2025-09-12T08:33:39.457Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:33:39.457Z
Learning: Be Frameworkの意味変数（VNBDL）は、日本古来の言霊（ことだま）思想と本質的類似性を持つ。言霊では「言葉に霊的な力が宿り現実に影響を及ぼす」が、意味変数では「名前に制約の力が宿り、現れただけで意味と制約が有効になる」。これにより単なる技術手法を超えた日本発の哲学的ソフトウェアパラダイムとして位置づけられる。
Applied to files:
manuals/1.0/ja/13-vision-ldd.mdmanuals/1.0/ja/03-being-classes.mdmanuals/1.0/ja/07-type-driven-metamorphosis.mdmanuals/1.0/ja/01-overview.md
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Use .html permalinks for cross-links in content (avoid linking to .md)
Applied to files:
manuals/1.0/en/03-being-classes.mdmanuals/1.0/en/04-final-objects.md
📚 Learning: 2025-09-12T08:21:12.233Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:21:12.233Z
Learning: Be Frameworkの意味変数アプローチは "Variable Name as a Business Domain Language (VNBDL)" と呼ばれ、Martin FowlerのCode As Documentationコンセプトの進化形として位置づけられている。変数名自体をビジネスドメイン言語の語彙とし、型システムレベルでドメインナレッジを実装する革新的なパラダイム。
Applied to files:
manuals/1.0/ja/01-overview.md
🪛 LanguageTool
manuals/1.0/ja/03-being-classes.md
[uncategorized] ~18-~18: 誤変換です。"自信"の間違いです。
Context: ... ## 内在と超越 存在クラスは変容が実際に起こる場所です。 オブジェクト自身が持つ性質（内在的性質（イマナンス））と、外部から提供される力（超越的な力（トランセン...
(JISINN)
manuals/1.0/en/12-philosophy-behind.md
[style] ~221-~221: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “reason” or “purpose”.
Context: ...son->validate($email); } } ``` ### Raison d'être French for "reason for being". The Rea...
(RAISON_D_ÊTRE)
[style] ~225-~225: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “reason” or “purpose”.
Context: ...be that existence: - ValidatedUser's raison d'être → Validation capability - SavedUser's...
(RAISON_D_ÊTRE)
[style] ~226-~226: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “reason” or “purpose”.
Context: ...→ Validation capability - SavedUser's raison d'être → Saving capability - DeletedUser's r...
(RAISON_D_ÊTRE)
[style] ~227-~227: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “reason” or “purpose”.
Context: ...e → Saving capability - DeletedUser's raison d'être → Deletion capability Each existence h...
(RAISON_D_ÊTRE)
manuals/1.0/en/03-being-classes.md
[style] ~42-~42: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...> Objects are reborn into the self they want to be, according to their own will (type d...
(REP_WANT_TO_VB)
[style] ~70-~70: Consider using a different adverb to strengthen your wording.
Context: ...he ingredients are the same, it becomes a completely new existence. - Immanent Factor: ...
(COMPLETELY_ENTIRELY)
[style] ~110-~110: Consider an alternative for the overused word “exactly”.
Context: ...formation process in the constructor is exactly the realization of Entelechy. `OrderCal...
(EXACTLY_PRECISELY)
[style] ~110-~110: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...d user. Each class becomes the "self it wants to be" in the constructor. In Be Framework...
(REP_WANT_TO_VB)
manuals/1.0/en/01-overview.md
[style] ~11-~11: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...objects to transform into the self they want to be, by their own will. Marcel Proust s...
(REP_WANT_TO_VB)
[style] ~16-~16: ‘In Search of’ might be wordy. Consider a shorter alternative.
Context: ...es. > > —Marcel Proust, 'The Prisoner' (In Search of Lost Time, Volume 5) 1923 ## Why Not a...
(EN_WORDINESS_PREMIUM_IN_SEARCH_OF)
[style] ~25-~25: Consider using a different adverb to strengthen your wording.
Context: ... system by itself. Be Framework adopts a completely different approach, incorporating the p...
(COMPLETELY_ENTIRELY)
[grammar] ~25-~25: Ensure spelling is correct
Context: ...ere one abandons artifice (control) and entrusts things to proceed to their natural stat...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
manuals/1.0/en/13-vision-ldd.md
[style] ~64-~64: ‘exactly the same’ might be wordy. Consider a shorter alternative.
Context: ...g in, the system can Reproduce (Replay) exactly the same metamorphosis process. ## Conclusion: ...
(EN_WORDINESS_PREMIUM_EXACTLY_THE_SAME)
manuals/1.0/en/04-final-objects.md
[style] ~158-~158: Consider an alternative for the overused word “exactly”.
Context: ...essential value of our system. This is exactly the destination of programming that Be ...
(EXACTLY_PRECISELY)
🪛 markdownlint-cli2 (0.18.1)
manuals/1.0/ja/13-vision-ldd.md
16-16: Blank line inside blockquote
(MD028, no-blanks-blockquote)
28-28: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
30-30: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
32-32: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
manuals/1.0/en/03-being-classes.md
28-28: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
29-29: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
30-30: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
manuals/1.0/en/01-overview.md
28-28: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
29-29: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
30-30: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
manuals/1.0/en/13-vision-ldd.md
13-13: Blank line inside blockquote
(MD028, no-blanks-blockquote)
manuals/1.0/ja/01-overview.md
28-28: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
29-29: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
30-30: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
🔇 Additional comments (15)
_includes/manuals/1.0/en/contents.html (1)
21-21: LGTM! Navigation update exposes the philosophy page.The removal of the
12-philosophy-behind.mdexclusion properly exposes the philosophy page in the manual navigation, aligning with the PR's objective to share the framework's philosophy internationally.Based on learnings, navigation contents are correctly updated when adding pages.
manuals/1.0/ja/04-final-objects.md (1)
162-162: LGTM! Link updated to match content reorganization.The hyperlink correctly uses the
.htmlpermalink format and aligns with the metamorphosis-patterns terminology used across the PR.As per coding guidelines, .html permalinks are used for cross-links in content.
manuals/1.0/ja/13-vision-ldd.md (1)
1-6: LGTM! Frontmatter is correctly configured.The layout (
docs-ja) and permalink are properly set for Japanese documentation.Based on learnings, manual pages correctly include the
docs-jalayout for Japanese.manuals/1.0/ja/03-being-classes.md (2)
24-43: Excellent addition of the Temporal Being narrative.The new section effectively frames objects as temporal beings with a lifecycle (Birth, Life, Becoming), enriching the philosophical foundation of Being Classes. The Entelechy concept and the "Becoming the self you want to be" framing are well-articulated.
68-68: LGTM! Formatting consistency improved.Removing the bold emphasis from the transformation pattern line maintains consistent formatting with similar content elsewhere in the documentation.
manuals/1.0/en/13-vision-ldd.md (1)
1-6: LGTM! Frontmatter is correctly configured.The layout (
docs-en) and permalink are properly set for English documentation.Based on learnings, manual pages correctly include the
docs-enlayout for English.manuals/1.0/ja/01-overview.md (1)
10-32: Excellent philosophical framing with Wu Wei and the Commander-to-Gardener metaphor.The new introduction effectively grounds Be Framework in Eastern philosophy and clearly articulates the shift from control-based to environment-based design. The "Becoming the self you want to be" framing provides a compelling narrative for the BEING-centric approach.
manuals/1.0/en/02-input-classes.md (1)
10-78: LGTM! Terminology refinements improve consistency.The updates from "Immanent Nature" to "Immanent" and the refined wording throughout the document improve clarity and align with the broader BEING-centric terminology used across the PR. The examples clearly illustrate the role of Immanence as the object's intrinsic identity.
manuals/1.0/en/01-overview.md (2)
10-32: Excellent English translation of the Wu Wei philosophy.The Commander-to-Gardener metaphor and the "Becoming the self you want to be" framing effectively communicate Be Framework's core philosophy. The English translation maintains the philosophical depth and clarity of the Japanese original.
34-109: Clear demonstration of the DOING-to-BEING paradigm shift.The examples effectively illustrate how focusing on states (BEING) rather than actions (DOING) leads to safer, more expressive code. The type system examples clearly show the compile-time safety benefits.
Note: The MD007 list indentation issue on lines 28-30 was previously addressed according to past review comments.
manuals/1.0/en/03-being-classes.md (2)
28-39: Fix Markdown list indentation to use 2 spaces.The nested list items use 4-space indentation, but the project Markdown linter (markdownlint-cli2) expects 2-space indentation for consistency. While this doesn't affect rendering, aligning with the linter configuration prevents CI warnings.
Apply this diff to correct the indentation:
### Lifecycle: Birth, Life, and "Becoming the self you want to be" 1. **Birth (Constructor)**: - * The constructor is where objects are born. Here, Immanence and Transcendence meet, and new Immanence is born. - * The moment it is born, the object's identity and state are determined and become Immutable. + * The constructor is where objects are born. Here, Immanence and Transcendence meet, and new Immanence is born. + * The moment it is born, the object's identity and state are determined and become Immutable. 2. **Life (Being)**: - * The object exposes its "form as it should be" to the world as `public readonly` properties. But no one touches those properties except its future self. - * This state is the crystallization of the encounter between Immanence and Transcendence. + * The object exposes its "form as it should be" to the world as `public readonly` properties. But no one touches those properties except its future self. + * This state is the crystallization of the encounter between Immanence and Transcendence. 3. **Becoming the self you want to be**: - * All transformations are journeys to become the final "Self you want to be (Final Object)". - * The Transcendence encountered influences the new Immanence and disappears. Like a childhood friend, they shape me and become part of me, but as a **temporal being only at that moment**, they are no longer there. - * The life of an object in Be Framework exists for this self-realization (Entelechy). + * All transformations are journeys to become the final "Self you want to be (Final Object)". + * The Transcendence encountered influences the new Immanence and disappears. Like a childhood friend, they shape me and become part of me, but as a **temporal being only at that moment**, they are no longer there. + * The life of an object in Be Framework exists for this self-realization (Entelechy).
149-149: Cross-link format verified.The link to the next manual correctly uses the
.htmlpermalink format per coding guidelines. ✓manuals/1.0/ja/07-type-driven-metamorphosis.md (1)
1-156: Excellent philosophical and technical clarity.This file's new "運命の地図としての型 (Destiny Map)" section is well-crafted. The progression from Type-Driven Metamorphosis to the Existential Question ("Who am I?") and the contrast between Routing (external control) versus Discovery (self-determination) is clear and compelling. The examples effectively demonstrate how union types encode an object's possible destinies without external conditionals. Cross-links and frontmatter are correct per guidelines. ✓
manuals/1.0/en/12-philosophy-behind.md (1)
1-410: Comprehensive philosophical integration; static analysis false positive dismissed.This document successfully bridges Eastern and Western philosophical traditions (Taoism, Buddhism, Heidegger, Aristotle, Spinoza) with Be Framework concepts. The progression from Ontological Programming → Temporal Being → Wu Wei → Entelechy → Sufficient Reason is intellectually rigorous and well-supported with code examples. Frontmatter and spelling are correct. ✓
Regarding the LanguageTool hint on "raison d'être": This is a false positive. The term is explicitly explained in context ("French for 'reason for being'") and is intentionally used in a philosophical section on Leibniz. Substituting generic synonyms would dilute philosophical precision. No change needed.
manuals/1.0/en/04-final-objects.md (1)
1-162: Compelling introduction of "Immanent Self-Proof" concept; cross-links verified.This manual effectively introduces Final Objects as temporal destinations and the novel concept of objects containing their own proof of completion (
$beenproperty withBeenProcessed/BeenRejected). This inverts traditional external testing toward ontological self-evidence—a sophisticated innovation aligned with the PR's philosophical objectives. The Zhuangzi epigraph is apt. Frontmatter and cross-link format are correct per guidelines. ✓
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
manuals/1.0/en/01-overview.md(2 hunks)manuals/1.0/ja/01-overview.md(4 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
manuals/1.0/@(en|ja)/**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
manuals/1.0/@(en|ja)/**/*.md: Place new manual pages as Markdown under manuals/1.0/en/ or manuals/1.0/ja/
Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Use .html permalinks for cross-links in content (avoid linking to .md)
Files:
manuals/1.0/en/01-overview.mdmanuals/1.0/ja/01-overview.md
🧠 Learnings (3)
📓 Common learnings
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to _includes/manuals/1.0/@(en|ja)/contents.html : Update navigation contents when adding pages (edit _includes/manuals/1.0/[lang]/contents.html)
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
📚 Learning: 2025-09-12T08:33:39.457Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:33:39.457Z
Learning: Be Frameworkの意味変数（VNBDL）は、日本古来の言霊（ことだま）思想と本質的類似性を持つ。言霊では「言葉に霊的な力が宿り現実に影響を及ぼす」が、意味変数では「名前に制約の力が宿り、現れただけで意味と制約が有効になる」。これにより単なる技術手法を超えた日本発の哲学的ソフトウェアパラダイムとして位置づけられる。
Applied to files:
manuals/1.0/ja/01-overview.md
📚 Learning: 2025-09-12T08:21:12.233Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:21:12.233Z
Learning: Be Frameworkの意味変数アプローチは "Variable Name as a Business Domain Language (VNBDL)" と呼ばれ、Martin FowlerのCode As Documentationコンセプトの進化形として位置づけられている。変数名自体をビジネスドメイン言語の語彙とし、型システムレベルでドメインナレッジを実装する革新的なパラダイム。
Applied to files:
manuals/1.0/ja/01-overview.md
🪛 LanguageTool
manuals/1.0/en/01-overview.md
[style] ~11-~11: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...objects to transform into the self they want to be, by their own will. Marcel Proust s...
(REP_WANT_TO_VB)
[style] ~16-~16: ‘In Search of’ might be wordy. Consider a shorter alternative.
Context: ...es. > > —Marcel Proust, 'The Prisoner' (In Search of Lost Time, Volume 5) 1923 ## From Doin...
(EN_WORDINESS_PREMIUM_IN_SEARCH_OF)
manuals/1.0/ja/01-overview.md
[uncategorized] ~96-~96: 「ことができる」という表現は冗長な可能性があります。
Context: ... ## このマニュアルで学べること 以下の新しいプログラミング手法を身につけることができます： 1. 「何をするか」ではなく「何であるか」を設計する 2. 不正な状態...
(DOUSI_KOTOGADEKIRU)
🪛 markdownlint-cli2 (0.18.1)
manuals/1.0/en/01-overview.md
89-89: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
90-90: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
manuals/1.0/ja/01-overview.md
89-89: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
90-90: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
9634ce7 to
20ab062
Compare
There was a problem hiding this comment.
Actionable comments posted: 3
♻️ Duplicate comments (3)
manuals/1.0/en/01-overview.md (1)
88-92: Fix critical list indentation violation.List items immediately following a heading should not be indented. Lines 89-90 have 2-space indentation which violates the MD007 linting rule.
Apply this diff:
### Commander to Gardener: - * The Commander orders subordinates (objects) to "Move!". But it is impossible to keep ordering all complex autonomous movements. - * The Gardener does not order plants. They only prepare the environment like water and light. +* The Commander orders subordinates (objects) to "Move!". But it is impossible to keep ordering all complex autonomous movements. +* The Gardener does not order plants. They only prepare the environment like water and light.manuals/1.0/ja/01-overview.md (1)
88-92: Fix critical list indentation violation.List items immediately following a heading should not be indented. Lines 89-90 have 2-space indentation which violates the MD007 linting rule and should be removed.
Apply this diff:
### Commander (司令官) から Gardener (庭師) へ: - * 司令官は、部下（オブジェクト）に「動け」と命令します。しかし、複雑な自律的な動きを全て命令し続けることは不可能です。 - * 庭師は、植物に命令しません。ただ、水や光という環境を整えるだけです。 +* 司令官は、部下（オブジェクト）に「動け」と命令します。しかし、複雑な自律的な動きを全て命令し続けることは不可能です。 +* 庭師は、植物に命令しません。ただ、水や光という環境を整えるだけです。manuals/1.0/ja/13-vision-ldd.md (1)
27-32: Fix list indentation for proper nesting under numbered items.Sub-items under numbered list items at lines 28, 30, and 32 have 2-space indentation but should have 4-space indentation to properly nest under their parent numbered items and conform to the MD007 linting rule. The English version of this file correctly uses 4-space indentation for the same structure.
Apply this diff:
1. **構造的透明性 (Structural Transparency)**: - * `#[Be]` 属性によって、変容のフローがコードの構造そのものとして明示されています。これにより、静的解析だけでアプリケーションの全遷移図（Decision Graph）を描くことが可能です。 + * `#[Be]` 属性によって、変容のフローがコードの構造そのものとして明示されています。これにより、静的解析だけでアプリケーションの全遷移図（Decision Graph）を描くことが可能です。 2. **意味的透明性 (Semantic Transparency)**: - * 変数名は単なるラベルではなく、契約です。`$email` という名前は `Email` クラスによる検証と思想的な定義（ALPSなど）を内包しています。これにより、変数名を見るだけでそのデータの「意味」と「保証」が分かります。 + * 変数名は単なるラベルではなく、契約です。`$email` という名前は `Email` クラスによる検証と思想的な定義（ALPSなど）を内包しています。これにより、変数名を見るだけでそのデータの「意味」と「保証」が分かります。 3. **実行透明性 (Execution Transparency)**: - * セマンティックログは、単なる「通過記録」ではなく、「なぜその決定に至ったか」という判断の根拠を全て記録します。 + * セマンティックログは、単なる「通過記録」ではなく、「なぜその決定に至ったか」という判断の根拠を全て記録します。
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (14)
.github/workflows/claude-code-review.yml(1 hunks)_includes/manuals/1.0/en/contents.html(1 hunks)_includes/manuals/1.0/ja/contents.html(1 hunks)manuals/1.0/en/01-overview.md(2 hunks)manuals/1.0/en/02-input-classes.md(3 hunks)manuals/1.0/en/03-being-classes.md(4 hunks)manuals/1.0/en/04-final-objects.md(4 hunks)manuals/1.0/en/12-philosophy-behind.md(1 hunks)manuals/1.0/en/13-vision-ldd.md(1 hunks)manuals/1.0/ja/01-overview.md(4 hunks)manuals/1.0/ja/03-being-classes.md(2 hunks)manuals/1.0/ja/04-final-objects.md(1 hunks)manuals/1.0/ja/07-type-driven-metamorphosis.md(1 hunks)manuals/1.0/ja/13-vision-ldd.md(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (5)
- manuals/1.0/ja/04-final-objects.md
- manuals/1.0/en/02-input-classes.md
- .github/workflows/claude-code-review.yml
- _includes/manuals/1.0/en/contents.html
- _includes/manuals/1.0/ja/contents.html
🧰 Additional context used
📓 Path-based instructions (1)
manuals/1.0/@(en|ja)/**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
manuals/1.0/@(en|ja)/**/*.md: Place new manual pages as Markdown under manuals/1.0/en/ or manuals/1.0/ja/
Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Use .html permalinks for cross-links in content (avoid linking to .md)
Files:
manuals/1.0/en/01-overview.mdmanuals/1.0/ja/01-overview.mdmanuals/1.0/ja/03-being-classes.mdmanuals/1.0/ja/07-type-driven-metamorphosis.mdmanuals/1.0/en/12-philosophy-behind.mdmanuals/1.0/en/13-vision-ldd.mdmanuals/1.0/en/04-final-objects.mdmanuals/1.0/en/03-being-classes.mdmanuals/1.0/ja/13-vision-ldd.md
🧠 Learnings (4)
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Applied to files:
manuals/1.0/ja/01-overview.mdmanuals/1.0/ja/13-vision-ldd.md
📚 Learning: 2025-09-12T08:33:39.457Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:33:39.457Z
Learning: Be Frameworkの意味変数（VNBDL）は、日本古来の言霊（ことだま）思想と本質的類似性を持つ。言霊では「言葉に霊的な力が宿り現実に影響を及ぼす」が、意味変数では「名前に制約の力が宿り、現れただけで意味と制約が有効になる」。これにより単なる技術手法を超えた日本発の哲学的ソフトウェアパラダイムとして位置づけられる。
Applied to files:
manuals/1.0/ja/01-overview.mdmanuals/1.0/ja/03-being-classes.mdmanuals/1.0/ja/07-type-driven-metamorphosis.mdmanuals/1.0/ja/13-vision-ldd.md
📚 Learning: 2025-09-12T08:21:12.233Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:21:12.233Z
Learning: Be Frameworkの意味変数アプローチは "Variable Name as a Business Domain Language (VNBDL)" と呼ばれ、Martin FowlerのCode As Documentationコンセプトの進化形として位置づけられている。変数名自体をビジネスドメイン言語の語彙とし、型システムレベルでドメインナレッジを実装する革新的なパラダイム。
Applied to files:
manuals/1.0/ja/01-overview.mdmanuals/1.0/ja/07-type-driven-metamorphosis.md
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Use .html permalinks for cross-links in content (avoid linking to .md)
Applied to files:
manuals/1.0/en/04-final-objects.mdmanuals/1.0/en/03-being-classes.md
🪛 LanguageTool
manuals/1.0/en/01-overview.md
[style] ~11-~11: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...objects to transform into the self they want to be, by their own will. Marcel Proust s...
(REP_WANT_TO_VB)
[style] ~16-~16: ‘In Search of’ might be wordy. Consider a shorter alternative.
Context: ...es. > > —Marcel Proust, 'The Prisoner' (In Search of Lost Time, Volume 5) 1923 ## From Doin...
(EN_WORDINESS_PREMIUM_IN_SEARCH_OF)
manuals/1.0/ja/01-overview.md
[uncategorized] ~96-~96: 「ことができる」という表現は冗長な可能性があります。
Context: ... ## このマニュアルで学べること 以下の新しいプログラミング手法を身につけることができます： 1. 「何をするか」ではなく「何であるか」を設計する 2. 不正な状態...
(DOUSI_KOTOGADEKIRU)
manuals/1.0/ja/03-being-classes.md
[uncategorized] ~18-~18: 誤変換です。"自信"の間違いです。
Context: ... ## 内在と超越 存在クラスは変容が実際に起こる場所です。 オブジェクト自身が持つ性質（内在的性質（イマナンス））と、外部から提供される力（超越的な力（トランセン...
(JISINN)
manuals/1.0/en/12-philosophy-behind.md
[style] ~221-~221: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “reason” or “purpose”.
Context: ...son->validate($email); } } ``` ### Raison d'être French for "reason for being". The Rea...
(RAISON_D_ÊTRE)
[style] ~225-~225: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “reason” or “purpose”.
Context: ...be that existence: - ValidatedUser's raison d'être → Validation capability - SavedUser's...
(RAISON_D_ÊTRE)
[style] ~226-~226: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “reason” or “purpose”.
Context: ...→ Validation capability - SavedUser's raison d'être → Saving capability - DeletedUser's r...
(RAISON_D_ÊTRE)
[style] ~227-~227: To make your text as clear as possible to all readers, do not use this foreign term. Possible alternatives are “reason” or “purpose”.
Context: ...e → Saving capability - DeletedUser's raison d'être → Deletion capability Each existence h...
(RAISON_D_ÊTRE)
manuals/1.0/en/13-vision-ldd.md
[style] ~64-~64: ‘exactly the same’ might be wordy. Consider a shorter alternative.
Context: ...g in, the system can Reproduce (Replay) exactly the same metamorphosis process. ## Conclusion: ...
(EN_WORDINESS_PREMIUM_EXACTLY_THE_SAME)
manuals/1.0/en/04-final-objects.md
[style] ~158-~158: Consider an alternative for the overused word “exactly”.
Context: ...essential value of our system. This is exactly the destination of programming that Be ...
(EXACTLY_PRECISELY)
manuals/1.0/en/03-being-classes.md
[style] ~42-~42: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...> Objects are reborn into the self they want to be, according to their own will (type d...
(REP_WANT_TO_VB)
[style] ~70-~70: Consider using a different adverb to strengthen your wording.
Context: ...he ingredients are the same, it becomes a completely new existence. - Immanent Factor: ...
(COMPLETELY_ENTIRELY)
[style] ~110-~110: Consider an alternative for the overused word “exactly”.
Context: ...formation process in the constructor is exactly the realization of Entelechy. `OrderCal...
(EXACTLY_PRECISELY)
[style] ~110-~110: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...d user. Each class becomes the "self it wants to be" in the constructor. In Be Framework...
(REP_WANT_TO_VB)
🪛 markdownlint-cli2 (0.18.1)
manuals/1.0/ja/01-overview.md
89-89: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
90-90: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
manuals/1.0/ja/07-type-driven-metamorphosis.md
120-120: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
122-122: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
manuals/1.0/en/13-vision-ldd.md
13-13: Blank line inside blockquote
(MD028, no-blanks-blockquote)
manuals/1.0/ja/13-vision-ldd.md
16-16: Blank line inside blockquote
(MD028, no-blanks-blockquote)
28-28: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
30-30: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
32-32: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
🔇 Additional comments (20)
manuals/1.0/ja/03-being-classes.md (4)
1-6: Frontmatter and structure comply with guidelines.Markdown layout correctly declares
layout: docs-jafor Japanese documentation, and the permalink uses proper.htmlformat per coding guidelines.
24-43: Temporal Being section well-integrates philosophical concepts from PR objectives.The new section introduces the lifecycle narrative (Birth → Life → Becoming) and frames objects as temporal entities that achieve self-realization through Entelechy. The structure is philosophically coherent and aligns with the PR's intent to communicate Wu Wei (non-doing via natural transformation) and the journey of "becoming the self one wants to be." The English-language quotation (lines 41–42) reinforces the bilingual framing of the PR.
149-149: Cross-links follow.htmlconvention.The link to the next manual page uses the proper
.htmlformat:[最終オブジェクト](./04-final-objects.html), consistent with coding guidelines and the broader documentation structure.
18-18: Static analysis warning on line 18 appears to be a false positive.LanguageTool flags line 18 suggesting confusion between "自信" (confidence) and "自身" (self/own), but the text correctly uses "自身" ("オブジェクト自身が持つ性質"), which is grammatically and semantically appropriate. The warning likely reflects a tool limitation rather than an actual error. The removal of bold emphasis on lines 18 and 68 appears intentional as part of the document's stylistic refinement.
Also applies to: 68-68
manuals/1.0/ja/07-type-driven-metamorphosis.md (2)
110-124: Philosophical integration thoughtfully elevates type-driven design with existential language.The new "運命の地図としての型 (Destiny Map)" section bridges technical type concepts with existential philosophy, framing union types as declarations of future possibilities and self-discovery. The introduction of "Who am I?" question, Destiny, and Self-Discovery aligns well with the PR's objective to present ontological programming concepts. The conceptual reframing of routing as self-illumination echoes the Wu Wei philosophy mentioned in the PR summary.
1-6: Frontmatter and document structure follow guidelines correctly.Layout is set to
docs-jaand the permalink uses the.htmlformat as required by coding guidelines.manuals/1.0/ja/01-overview.md (1)
1-6: Frontmatter and layout are correct.The docs-ja layout and .html permalink format follow guidelines correctly.
manuals/1.0/en/03-being-classes.md (2)
1-6: Frontmatter and cross-links are correctly formatted.The docs-en layout and .html permalinks follow guidelines properly.
10-45: Excellent execution of Immanence/Transcendence framing.The philosophical terminology and examples (Laozi quote, Immanence, Transcendence, Temporal Being) are well-integrated and consistent with the PR's ontological shift. The code examples effectively demonstrate the concept.
manuals/1.0/ja/13-vision-ldd.md (1)
1-6: Frontmatter layout is correct.The docs-ja layout and .html permalink format follow guidelines.
manuals/1.0/en/13-vision-ldd.md (2)
1-6: Frontmatter and layout are correct.The docs-en layout and .html permalink format follow guidelines.
20-30: List nesting is properly formatted.The nested list items under numbered points use correct 4-space indentation per markdown standards and pass linting validation.
manuals/1.0/en/01-overview.md (2)
1-6: Frontmatter and cross-link format are correct.The docs-en layout and .html permalink usage follow guidelines properly.
10-34: Philosophical introduction is well-crafted.The Proust quotation and shift from "Doing to Being" framework effectively establish the ontological foundation for the manual. The DeletedUser example clearly illustrates the paradigm shift.
manuals/1.0/en/04-final-objects.md (3)
1-6: Frontmatter and cross-link format are correct.The docs-en layout and .html permalink follow guidelines correctly. The cross-link on line 162 is properly formatted.
10-20: Philosophical framing and journey concept are well-executed.The Zhuangzi quote, Final Object definition, and Entelechy concept effectively communicate the destination of metamorphosis. The contrast between Pure Identity and Rich Transformed State clearly illustrates the progression.
42-75: Self-proof concept with BeenProcessed/BeenRejected is clear.The code examples effectively demonstrate immanent self-proof through the
$beenproperty, aligning well with the PR's philosophical shift away from external testing toward object-intrinsic evidence.manuals/1.0/en/12-philosophy-behind.md (3)
1-8: Frontmatter and overall structure are excellent.The docs-en layout is correct, and the document provides comprehensive philosophical grounding for Be Framework, integrating Eastern and Western traditions effectively.
10-120: Philosophy integration is well-conceived and rigorously developed.The layered exploration of Ontological Programming, Temporal Being (Heidegger's Dasein), Wu Wei, Entelechy, Principle of Sufficient Reason, Immanence/Transcendence, and Buddhist Dependent Origination creates a robust philosophical foundation. Code examples for each concept (UserInput, LoanApplication, PaymentAttempt) effectively ground abstract philosophy in concrete implementation.
374-410: Paradigm evolution and future vision are compelling.The progression from "Machine Language" through "Ontological Era" clearly articulates how Be Framework addresses the AI-enabled future, where humans define meaning and existence while AI optimizes implementation. The closing metaphor about code as philosophy and engineers as philosophers provides appropriate resonance with the PR's ontological vision.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
manuals/1.0/ja/01-overview.md (1)
94-96: Minor style consideration: Potential verb redundancy.Line 96 uses "身につけることができます" (acquire the ability to...). LanguageTool suggests this verb construction may be slightly redundant. If conciseness is preferred, alternatives like "身につけられます" or "習得できます" could be considered, though the current phrasing is grammatically natural and clear.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
manuals/1.0/en/01-overview.md(2 hunks)manuals/1.0/ja/01-overview.md(4 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
manuals/1.0/@(en|ja)/**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
manuals/1.0/@(en|ja)/**/*.md: Place new manual pages as Markdown under manuals/1.0/en/ or manuals/1.0/ja/
Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Use .html permalinks for cross-links in content (avoid linking to .md)
Files:
manuals/1.0/en/01-overview.mdmanuals/1.0/ja/01-overview.md
🧠 Learnings (4)
📓 Common learnings
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to _includes/manuals/1.0/@(en|ja)/contents.html : Update navigation contents when adding pages (edit _includes/manuals/1.0/[lang]/contents.html)
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Place new manual pages as Markdown under manuals/1.0/en/ or manuals/1.0/ja/
📚 Learning: 2025-09-12T01:10:59.522Z
Learnt from: CR
Repo: be-framework/be-framework.github.io PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-12T01:10:59.522Z
Learning: Applies to manuals/1.0/@(en|ja)/**/*.md : Manual pages must include correct layout in frontmatter: docs-en for English, docs-ja for Japanese
Applied to files:
manuals/1.0/ja/01-overview.md
📚 Learning: 2025-09-12T08:33:39.457Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:33:39.457Z
Learning: Be Frameworkの意味変数（VNBDL）は、日本古来の言霊（ことだま）思想と本質的類似性を持つ。言霊では「言葉に霊的な力が宿り現実に影響を及ぼす」が、意味変数では「名前に制約の力が宿り、現れただけで意味と制約が有効になる」。これにより単なる技術手法を超えた日本発の哲学的ソフトウェアパラダイムとして位置づけられる。
Applied to files:
manuals/1.0/ja/01-overview.md
📚 Learning: 2025-09-12T08:21:12.233Z
Learnt from: koriym
Repo: be-framework/be-framework.github.io PR: 0
File: :0-0
Timestamp: 2025-09-12T08:21:12.233Z
Learning: Be Frameworkの意味変数アプローチは "Variable Name as a Business Domain Language (VNBDL)" と呼ばれ、Martin FowlerのCode As Documentationコンセプトの進化形として位置づけられている。変数名自体をビジネスドメイン言語の語彙とし、型システムレベルでドメインナレッジを実装する革新的なパラダイム。
Applied to files:
manuals/1.0/ja/01-overview.md
🪛 LanguageTool
manuals/1.0/en/01-overview.md
[style] ~11-~11: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...objects to transform into the self they want to be, by their own will. Marcel Proust s...
(REP_WANT_TO_VB)
[style] ~16-~16: ‘In Search of’ might be wordy. Consider a shorter alternative.
Context: ...es. > > —Marcel Proust, 'The Prisoner' (In Search of Lost Time, Volume 5) 1923 ## From Doin...
(EN_WORDINESS_PREMIUM_IN_SEARCH_OF)
manuals/1.0/ja/01-overview.md
[uncategorized] ~96-~96: 「ことができる」という表現は冗長な可能性があります。
Context: ... ## このマニュアルで学べること 以下の新しいプログラミング手法を身につけることができます： 1. 「何をするか」ではなく「何であるか」を設計する 2. 不正な状態...
(DOUSI_KOTOGADEKIRU)
🔇 Additional comments (10)
manuals/1.0/en/01-overview.md (5)
1-6: Frontmatter is correctly configured.Layout is properly set to
docs-enand permalink uses the.htmlformat as required by coding guidelines.
10-16: Strong philosophical foundation with clear examples.The introduction effectively frames the "Becoming" concept with the Proust epigraph, establishing the intellectual foundation for the Wu Wei and BEING-focused philosophy introduced later. The code example (DeletedUser) clearly illustrates the shift from imperative actions to object states.
36-78: Clear progression from DOING to BEING with strong code examples.The section systematically introduces type-based state design. The ValidatedUser → SavedUser → DeletedUser progression effectively shows temporal transformation through the type system, which is a core objective of this PR. The comparison of generic User vs. specific state types (ValidatedUser, SavedUser, DeletedUser) makes the paradigm shift concrete and actionable.
80-92: Wu Wei philosophy and Commander-to-Gardener metaphor are well-articulated.The section introduces the Eastern philosophy of Wu Wei (Non-doing) and contrasts the Controller paradigm with environmental preparation—core PR objectives. List indentation is now correct (no leading spaces), and the Metamorphosis concept ties autonomous transformation back to the BEING-focused design introduced earlier. The metaphor effectively communicates the shift from command-and-control to environment cultivation.
94-107: Learning outcomes and navigation are aligned with PR philosophy.The numbered learning outcomes directly map to the concepts introduced (BEING, invalid state prevention, autonomous transformation, trust over prevention). The relative URL to Input Classes is correctly formatted using Jekyll syntax, and the call-to-action text reinforces the experiential learning approach. No markdown or URL issues detected.
manuals/1.0/ja/01-overview.md (5)
1-6: Frontmatter is correctly configured for Japanese manual.Layout is properly set to
docs-jaand permalink uses the.htmlformat, matching English version structure and coding guidelines.
10-34: Japanese introduction parallels English version with proper localization.The opening frames "Becoming the self you want to be" (なりたい自分になる) with the Proust epigraph, and the DeletedUser example is consistent with the English version. The transition text ("実はこの疑問が、プログラミングの新しい世界への入り口です") effectively signals the philosophical shift.
36-78: Clear BEING-focused progression with consistent code examples.The Japanese section mirrors the English version's logical flow: DOING introduction → BEING approach → why it matters → type-based state design. The explanation of "自らが最終オブジェクトになる" (becoming the final object) clearly conveys the state-transformation concept central to the PR objectives.
80-92: Wu Wei philosophy and Commander-to-Gardener metaphor are effectively localized.The Japanese section explains 無為自然 (Wu Wei / Non-doing) and contrasts the command-and-control Controller with environmental preparation for autonomous transformation (自己変容). List indentation is now correct (no leading spaces), and the gardener metaphor ("庭師は、植物に命令しません") translates the concept clearly. This section aligns with core PR objectives of introducing Eastern philosophical concepts to frame the BEING-focused paradigm.
94-107: Learning outcomes and call-to-action are clear and properly structured.The four numbered outcomes directly map to PR objectives (BEING design, invalid state prevention, natural transformation, trust over error prevention). The relative URL to Input Classes uses correct Jekyll syntax, and the closing invitation to experience DeletedUser reinforces the hands-on philosophy. No markdown or URL issues detected.
|
@coderabbitai Fixed markdown linting issues: removed empty blockquote lines (MD028) in 13-vision-ldd.md (ja/en), fixed list indentation in 07-type-driven-metamorphosis.md (ja), and removed leading spaces from list items in 01-overview.md (ja/en). |
|
Tip For best results, initiate chat on the files or code changes. @koriym Thank you for fixing those markdown linting issues! It's great that you've addressed the MD028 violations, list indentation, and leading spaces across both the English and Japanese documentation. These fixes will help maintain consistent formatting standards throughout the manuals. If you found this review helpful, would you consider giving us a shout-out on X? Thank you for using CodeRabbit! |
1 participant
Translates the core Be Framework manuals into English to share its unique philosophy with the world.
This PR introduces the foundational concepts of Ontological Programming:
These documents are not just instructions; they are an invitation to a new way of thinking about code.
Summary by CodeRabbit
Documentation
Chores
✏️ Tip: You can customize this high-level summary in your review settings.