FPF

First Principles Framework (FPF) - Core Conceptual Specification

408 patterns · 10726 sections

Choose a heading to read that text in full, or open the complete publication.

Table of contents

Overview · All sections
  1. First Principles Framework (FPF) - Core Conceptual Specification
  2. Table of Contents
  3. First Principles Framework (FPF) Readme
  4. Start here
  5. Practical entries
  6. LIVE-WORK-STEERING — Choose the next action while Work is changing
  7. METHOD-RECOVERY — Explain what reusable way several performances may show
  8. PROFESSIONAL-RESULT — Use one result from another practice without transferring the decision
  9. NAMING — Give one identified thing a usable name
  10. SYSTEM-RECOGNITION — Test systemhood only when it changes the decision
  11. TIME — Determine what a timing claim establishes
  12. CAUSAL-USE — Explain an outcome or derive an intervention consequence
  13. MEASUREMENT — Make a number interpretable before relying on it
  14. MATHEMATICAL-MODELING — Obtain a useful consequence from a representation
  15. METHOD-CONSTRUCTION — Construct, connect and change methods for practical use
  16. WORK-OPPORTUNITY — Find a useful continuation before proposing change
  17. COMMUNICATION-FOR-USE — Make communication useful, then learn from what happens
  18. RESULT-TO-NEXT-MOVE — Route an obtained result to the next probe or option
  19. ACTUAL-TEMPORAL-STRUCTURE — Recover what actually obtains before testing coordination
  20. CONSEQUENCE-BEARERS — Find omitted Systems before closing a decision
  21. Practical-Use Cards
  22. UNFAMILIAR-THEORY - Make an unfamiliar theory usable
  23. PHYSICAL-RESULT - Connect physics, mathematics and computation
  24. Expansion for PHYSICAL-RESULT
  25. ARCHITECTURE — Carry an outside need through structure and feedback
  26. PRACTICE-ARCHITECTURE — Connect methods with their use, support and development
  27. WORKING-DOCUMENTS — Make a document support its intended uses
  28. OPTION-COMPARISON — Keep unlike option results distinct
  29. PROBLEM-SHAPING — Formulate the problem the work needs
  30. IMPROVEMENT — Define better before repeating change
  31. WORDING — Repair language without replacing the project question
  32. SOTA-PORTFOLIO — Compare approaches that could answer your question
  33. SYSTEM-DELIMITATION — Separate parts, selected boundary, and crossings
  34. Decide Whether FPF Fits
  35. When Several Transformation Flows Form One Network
  36. Perform several levels of work through one action
  37. Recover a lost path from outside use to recursive builders
  38. One-Minute Example
  39. What FPF Is
  40. What FPF Is Not
  41. How to Use This Repository
  42. License and reuse
  43. Citation
  44. First Principles Framework Architectural Reference (non-normative)
  45. FPF.Reference:1 - What This Specification Is And How To Use It
  46. FPF.Reference:1.1 - Four ordinary starts before a PatternID
  47. FPF.Reference:2 - FPF As A Project, Not Only A Pattern List
  48. FPF.Reference:3 - Why FPF Exists
  49. FPF.Reference:4 - Creativity And Assurance Mature Together
  50. FPF.Reference:5 - Local Closure Inside An Open World
  51. FPF.Reference:6 - FPF As An Evolutionary Architecture For Thought
  52. FPF.Reference:7 - Architectural Characteristics Of Thought
  53. FPF.Reference:8 - Beyond Bias Hunting
  54. FPF.Reference:9 - Thinking Through Writing
  55. FPF.Reference:10 - Thinking-Oriented Architecture, Not A Descriptive Upper Ontology
  56. FPF.Reference:11 - When A Scale Claim Calls For Comparison
  57. FPF.Reference:12 - Descriptions, Views And Publication Forms
  58. FPF.Reference:13 - Architecture As Structure Of Holons
  59. FPF.Reference:14 - Boundary Statements
  60. FPF.Reference:15 - Raising Semantic Precision
  61. FPF.Reference:16 - Big FPF Storylines
  62. FPF.Reference:16.1 - Follow one question through several contributions
  63. FPF.Reference:16.2 - Architectural Rationale
  64. FPF.Reference:16.3 - Shared sources and the choices they support
  65. FPF.Reference:16.4 - What to examine when adapting the arrangement
  66. FPF.Reference:16.5 - Construct a usable whole with existing methods
  67. FPF.Reference:16.5.1 - Start outside the proposed boundary
  68. FPF.Reference:16.5.2 - Recover the construction and select the next operation
  69. FPF.Reference:16.5.3 - Compare constructions and return to use
  70. FPF.Reference:16.5.4 - Explanation and night coverage
  71. FPF.Reference:16.5.4.1 - Recover the receiving result
  72. FPF.Reference:16.5.4.2 - Compare proposed ways to meet the need
  73. FPF.Reference:16.5.4.3 - Specify the missing procurement and operating results
  74. FPF.Reference:16.5.4.4 - Return the result and its remaining conditions
  75. FPF.Reference:16.5.5 - An interpretable pressure assessment
  76. FPF.Reference:16.5.5.1 - Recover the pressure question and its inputs
  77. FPF.Reference:16.5.5.2 - Form and interpret the pressure assessment
  78. FPF.Reference:16.5.5.3 - Change the input and retain the applicable reasoning
  79. FPF.Reference:16.6 - Develop a useful way from received material
  80. FPF.Reference:16.7 - Develop and use methods with distinct claims and results
  81. FPF.Reference:16.7.1 - Method, MethodDescription, WorkPlan, and Work remain distinct
  82. FPF.Reference:16.7.2 - Several structures and several views can coexist
  83. FPF.Reference:16.7.3 - Reader route and result dependencies do not prescribe Work order
  84. FPF.Reference:16.7.4 - Status, evidence, and assurance decisions are preserved
  85. FPF.Reference:16.7.5 - What this Method-development family foregrounds and leaves outside
  86. FPF.Reference:16.7.6 - Why these Method-development questions stay separate
  87. FPF.Reference:16.8 - Produce pattern-language knowledge and use it under changing conditions
  88. FPF.Reference:16.8.1 - Situation, problem and first gain
  89. FPF.Reference:16.8.2 - Production and situated use are different contributions
  90. FPF.Reference:16.8.3 - Unfolding a use, including a changed situation
  91. FPF.Reference:16.8.4 - Practical checks, recurring failures and costs
  92. FPF.Reference:16.8.5 - Architectural Rationale and source comparison
  93. FPF.Reference:16.8.6 - Relations and scope of the whole account
  94. FPF.Reference:16.9 - Choose the Method-development result needed for release EC-417
  95. FPF.Reference:16.9.1 - 1. Bound the EC-417 receiving result and recover the subjects of its management accounts
  96. FPF.Reference:16.9.2 - 2. Choose the subject before redesigning it
  97. FPF.Reference:16.9.3 - 3. Separate observed differentiation, causal support, and today’s decision
  98. FPF.Reference:16.9.4 - 4. Recover candidate accounts only when ordinary Method recovery is insufficient
  99. FPF.Reference:16.9.5 - 5. Build the repertoire and criteria without preselecting an architecture
  100. FPF.Reference:16.9.6 - 6. Recover package contributions and qualify individual subjects

Showing 1–100 of 10726 entries. Source edition 7a93d8f8122b.