Documentation Theory: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
*Both final results and in-process learnings qualify as work product. | *Both final results and in-process learnings qualify as work product. | ||
*Scalability of collaboration has no limits. | *Scalability of collaboration has no limits. | ||
*AI may assist in synthesis of in-process work to further refine work product. | |||
*For composed CAD at product level (hundreds of parts) - create part trees with [[Visualization Priority]], not [[Taxonomy Priority]]. | *For composed CAD at product level (hundreds of parts) - create part trees with [[Visualization Priority]], not [[Taxonomy Priority]]. | ||
*Version Product by number, so it can be found when dates, locations, or other descriptors are not available. This is for purposes of long-term management and degeneracy, simply by knowing [[Product Nomenclature]]. | *Version Product by number, so it can be found when dates, locations, or other descriptors are not available. This is for purposes of long-term management and degeneracy, simply by knowing [[Product Nomenclature]]. | ||
*Design documentation taxonomy in a fashion that allows any outsider to Orient themselves fully to find any documentation asset whatsoever no matter how granular, simply by understanding basic principles of OSE taxonomy. | *Design documentation taxonomy in a fashion that allows any outsider to Orient themselves fully to find any documentation asset whatsoever no matter how granular, simply by understanding basic principles of OSE taxonomy. | ||
*Remember always that the goal is [[Integration by Degeneracy]] | *Remember always that the goal is [[Integration by Degeneracy]] | ||
Revision as of 18:45, 1 March 2025
- Work product documentation for each contributor must be indexed in a single, permanent, public venue. Index must follow best practices of collaborative literacy and taxonomy.
- Both final results and in-process learnings qualify as work product.
- Scalability of collaboration has no limits.
- AI may assist in synthesis of in-process work to further refine work product.
- For composed CAD at product level (hundreds of parts) - create part trees with Visualization Priority, not Taxonomy Priority.
- Version Product by number, so it can be found when dates, locations, or other descriptors are not available. This is for purposes of long-term management and degeneracy, simply by knowing Product Nomenclature.
- Design documentation taxonomy in a fashion that allows any outsider to Orient themselves fully to find any documentation asset whatsoever no matter how granular, simply by understanding basic principles of OSE taxonomy.
- Remember always that the goal is Integration by Degeneracy