nucleation

design-rationale

Graph View

61 items with this tag.

Oct 28, 2026
ARG-028: Inbound references per code and turns per filed entry show which structures anchor and that drift falls as anchoring keeps up with arrival
- design-rationale
- epistemology
Oct 28, 2026
CASE-183: The anchoring measures: inbound references per code and turns per filed entry, counted in the record's own grammar
- design-rationale
- epistemology
Oct 27, 2026
CASE-178: How the record's grammar grows: after its scaffold, this record filed documents on all 32 days, added vocabulary terms on 18, fields or relations to schemes on 8, whole vocabularies on 3, schemes on 1 and a remote project on 1, so the owner's ordering of levels holds by frequency; but each refinement came in the same pull request as the documents that needed it and, nine times in ten, an ADR, so the levels are rarer events of one loop of work, not slower processes of their own, and the grammar's rates fell while filing rose
- design-rationale
- complex-systems
Oct 27, 2026
CASE-180: The record's own rates: over its first fifty days, measured from git, an entry's prose is revised about once in 22 days once drafting is over, its status once in 128, an authored relation gained or lost once in 132 and an authored relation retracted once in about 600, while no relation type has been redeclared; the layers' event rates are ordered as the exchange guessed, but only after the first day, when all of them change together, and the grammar is slow to revise without being slow to grow
- design-rationale
- complex-systems
Oct 27, 2026
CLAIM-469: Luria is an apparatus for a record's objects in the operational sense: through its schemes, vocabularies, validators and generated views it realizes a system of distinctions that fixes what counts as a referable and governable object within the record, so that a split scheme makes one object two and a promoted vocabulary makes a value an entity; it keeps, enforces and propagates those distinctions; and its distinctions are revised through the record's own use
- design-rationale
- epistemology
Oct 27, 2026
CLAIM-470: Inquiry is a form of specification: a question fixes which differences would count as an answer, an inquiry adds the operations that make those differences accessible, and what it finds can stabilize into a specification that constrains later inquiry; so inquiry stands to its findings as a specification to its realizations, with one difference, that an inquiry can revise what an answer could be
Oct 27, 2026
CLAIM-472: Because an apparatus makes some distinctions determinate and leaves others unstatable, choosing and maintaining one is open to evaluation and not only to verification; but that a cut excludes something fixes no obligation, since every distinction excludes, and which exclusions matter is a judgment indexed to a standard, a scale and those affected
Oct 27, 2026
CLAIM-475: Specifying is itself a resource-bounded realization: formulating a question takes time, concepts and computation as realizing a configuration takes energy and matter, so the questions an agent can ask are a product of what it has already realized; a stabilized specification is past inquiry stored so that later questions become cheaper to ask, and it can make other questions harder
Oct 27, 2026
CLAIM-476: Beyond what it does operationally, luria is an apparatus in Barad's constitutive sense for the objects of a record, and only for them: the record's objects are constituted, and not only made referable and governable, by the distinctions its grammar enacts, so that the same authored material is a different set of objects under a revised apparatus, and the record's own inquiry reconstitutes the apparatus that constitutes them
Oct 27, 2026
CLAIM-479: In the record a typed relation is more constrained than either of its relata: a claim's content is open prose, while rests_on fixes the scheme at both ends, has supports written as its converse and says what retiring its target leaves, and none of that moves when either claim's content does; so a relation's rigidity is a fact about the grammar, not evidence that the dependency it records is sound
Oct 27, 2026
CLAIM-483: An argument developed with collaborators who keep no memory fails mainly at identity and not at structure, so that coding what recurs, not argument mapping, is the remedy, and this holds beyond one owner and one assistant family
- design-rationale
- epistemology
Oct 27, 2026
LIT-1631: Sorting Things Out: Classification and Its Consequences
Oct 27, 2026
QUESTION-283: Can composing systems create an effective structure whose adequate specification needs a richer relational vocabulary than the parts needed separately (relations of higher arity, history, or a new kind) and, if so, under what conditions, and is the new vocabulary forced by the composite or only by the restricted class of descriptions in use?
Oct 27, 2026
TERM-089: apparatus, in the operational sense: a realized organization that selectively couples differences in one system to distinguishable outcomes in another; by function it may differentiate, retain, enforce and revise, and the four come apart
Oct 27, 2026
TERM-091: relational vocabulary, of a class of descriptions: the arities and kinds of relation it can state (pairwise or higher-order, among states or among histories, of which declared types), and so which constraints are expressible in it at all
Oct 22, 2026
CASE-131: The graph that asserted an inference nobody made: filing one claim as supporting another made the record's link fixer write that the other rested on it, and the record answered by adding a relation
- design-rationale
- epistemology
Oct 22, 2026
CLAIM-419: The record's grammar is fixed at any moment but amendable by decision, and in practice a move that fit no scheme or relation has repeatedly been treated as a defect of the grammar and answered by amending it, so a move the grammar cannot hold is not only forced or lost; whether every such move is caught is not shown
- design-rationale
- epistemology
Oct 22, 2026
QUESTION-258: Should a manuscript drawn from the record be chosen as a well-supported connected part of its argument, or as a smallest set of claims that changes what the argument can conclude, and what else must the choice preserve?
Oct 15, 2026
CASE-088: The repeated objection and the argument nobody reuses: filing pays for itself after a few recurrences in one case, and never in the other
- design-rationale
Oct 15, 2026
CASE-091: A memory ablation for revision: synthetic inquiries with known ground truth, run under six kinds of persistent memory, with information and token budget controlled separately
- epistemology
- design-rationale
Oct 15, 2026
CLAIM-295: A record of an inquiry's justifications adds nothing for decisions its current state already suffices for: what it can add is a wider family of decisions for which what is kept suffices, and decisions a bounded agent can make that it otherwise could not
- epistemology
- design-rationale
Oct 15, 2026
CLAIM-299: Decision sufficiency, historical accountability and correctness are three properties of a record of inquiry, and each can hold while the other two fail
- epistemology
- design-rationale
Oct 15, 2026
CLAIM-303: Filing an argument moves work across time: it is paid for now, in filing, indexing, tracking dependencies and checking it is still current, against reconstruction later, so it is worth its cost only when expected reuse covers it, and recurrence is evidence of reuse, not the criterion
- design-rationale
- epistemology
Oct 15, 2026
CLAIM-308: Where reuse cannot be forecast, recurrence weighted by reconstruction cost is the filing criterion, not only evidence for one: filing at the first use at which reconstructing again would take the overpayment past the cost of filing is within 2 − (c_a + u)/c_r of the hindsight optimum on every sequence of uses, at most twice, and no deterministic rule without foresight guarantees materially better, under fixed known costs, with staleness left out and the cost of recognizing what a filed argument answers taken as fixed
- design-rationale
- epistemology
Oct 15, 2026
CLAIM-313: A fixed number of bins realizes one partition only when each item is stored once: with copies, overlapping partitions coexist, as hashing-based similarity search stores each item in many partitions and pays for it in space, so sortings conflict as arrangements only under a one-copy constraint, which binds bricks but not index entries
Oct 15, 2026
CLAIM-314: Reusing a filed argument has a recognition cost that a fixed per-use price leaves out: certifying that stored answers cover a new question is NP-complete even for conjunctive queries, grows with the number and size of the stored definitions rather than being a constant per item, and is undefined for an item filed without a statement of what it answers, so each filing raises the cost of later reuse and per-item break-even decisions are not independent
Oct 15, 2026
CLAIM-324: In the What Survives Translation? exchange, the manuscript drafted straight from the crystallized argument changed the thesis with no turn arguing the move and dropped 24 of that argument's items, none on request, and the second crystallized argument announced its change of question but left items out without saying which had dissolved and which were lost
- design-rationale
- epistemology
Oct 15, 2026
QUESTION-098: When is an inferential structure worth filing: when does the reconstruction it is expected to save outweigh the cost of filing it, keeping it current and the risk of reusing it after it has gone stale?
- design-rationale
- epistemology
Oct 15, 2026
QUESTION-108: When a structured record does better than a summary, a transcript or a posterior on revision tasks, is it because it retains more, because what it retains is easier to reach, or because the operations a reviser needs are easier to perform on it?
- epistemology
- design-rationale
Oct 14, 2026
THEORY-311: Groupware that requires extra work from members who do not perceive a direct benefit from it, where that work is not made part of their job, is resisted or goes unused, and the applications that succeed in groups without a mandate give each user who does the work a benefit of their own
- design-rationale
- social-science
Oct 12, 2026
CLAIM-190: The anchoring measures are computed in the grammar that shapes the argument, so by themselves they cannot certify that drift fell: drift must also be judged under standards the record did not supply
- design-rationale
- epistemology
Oct 12, 2026
CLAIM-192: A multi-session argument's thesis can move without any participant arguing for the move, which is a case of an organized whole's course coming apart from its members' intentions
- design-rationale
- social-ontology
Oct 12, 2026
CLAIM-250: What a developing argument should preserve through legitimate revision is its accountability structure, what was asserted, why, how it was challenged and what justified its revision, not its propositions, so fidelity is defined over justificatory and provenance relations while propositional content changes
- design-rationale
- epistemology
Oct 12, 2026
QUESTION-064: Does an anchor need endorsement as well as addressability, stable identity and discoverability: are entries the record has not accepted built on less than entries it has?
- design-rationale
- epistemology
Oct 12, 2026
QUESTION-072: Does a project memory distribute credibility among an argument's contributors, by making some contributors' moves addressable and leaving others' as unfiled turns, so that what gets a code gets cited and what does not is re-derived or lost?
Oct 11, 2026
CLAIM-176: Recurrence is the trigger of persistence this record is built around: coding a thing the second time it turns up captures exactly the drift that defeats an argument, and keeps capture from flooding the record
- design-rationale
- epistemology
Oct 11, 2026
CLAIM-177: In the record's exchanges with collaborators who keep no memory, the argument repeatedly loses identity: concepts are redefined silently, objections and readings come back as though new, and the thesis changes without anyone arguing for the change
- design-rationale
- epistemology
Oct 11, 2026
CLAIM-178: A manuscript should be a view over the argument and not its only copy: a draft written straight from an exchange drops commitments and changes its thesis without saying so, and both become visible only against a record where claims carry status and inclusion separately
- design-rationale
- epistemology
Oct 11, 2026
CLAIM-179: When an agent does the filing, the cost of capturing argument falls on the party that would otherwise pay to re-derive it, which removes the disparity that design-rationale systems were abandoned over
- design-rationale
Oct 11, 2026
CLAIM-180: Drift is retrieval failure outside a critical distance: a restatement close enough to an idea retrieves it, one that has drifted too far is taken for new, and a code bypasses retrieval by content altogether
- design-rationale
- epistemology
Oct 11, 2026
CLAIM-181: The record fixes the grammar an argument is expressed in, though not its shape: its closed vocabulary of schemes, roles and relations formalizes early, and a move that fits no CLAIM, TERM, ARG or declared relation is forced into one or lost until the misfit is noticed and the grammar amended to hold it
- design-rationale
- epistemology
Oct 11, 2026
CLAIM-182: Storage is not anchoring, addressability is: a structure that is kept but cannot be pointed at part by part does not stop re-derivation, and the same content becomes an anchor once its parts get addresses
- design-rationale
- epistemology
Oct 11, 2026
CLAIM-183: Generated views of the record, fed back into the exchange, become instruments of the argument: they show where its terms evolved faster than its formalism
- design-rationale
- epistemology
Oct 11, 2026
CLAIM-184: Anchors entrench: a structure that persists early can lock in its framing, so that later structure grows on it and alternatives become hard to reach, and retirement by status is the record's remedy only if superseded anchors stop attracting new structure
- design-rationale
- epistemology
Oct 11, 2026
CLAIM-185: The nucleation threshold of an argument is whatever makes a structure persist: a persistent structure is available as an anchor, and more complex structure can evolve only on anchors
- design-rationale
- epistemology
Oct 11, 2026
CLAIM-186: How fast an argument grows sets how it grows: drift tracks how fast new material arrives relative to how fast it is anchored, so a fast, prolific exchange branches, as a crystal grown far from equilibrium does, and a project memory stabilizes an argument by keeping anchoring up with arrival
- design-rationale
- epistemology
Oct 11, 2026
CLAIM-189: Fidelity is the wrong measure of a developing argument: maturing drops and changes things legitimately, so what a record can secure is traceability, change that is announced and located, not preservation
- design-rationale
- epistemology
Oct 11, 2026
CLAIM-191: Restating an argument across memoryless sessions is iterated transport with only a weak channel back to the source: without anchors, restatements drift toward the collaborators' own framings rather than at random, and a code restores continuity of transmission
- design-rationale
- epistemology
Oct 11, 2026
CLAIM-195: For an argument, the constraint set that persistence is relative to is fixed by an amendable decision, not discovered: the record stipulates what counts as the same claim persisting, which makes the choice explicit without making it non-arbitrary
- design-rationale
- epistemology
Oct 11, 2026
QUESTION-037: When an argument is developed across sessions with collaborators who keep no memory, what makes it settle into a stable structure, and what can a project memory contribute?
- design-rationale
- epistemology
Oct 11, 2026
QUESTION-038: What turns a structure that persists into an anchor that later structure can be built on?
- design-rationale
- epistemology
Oct 11, 2026
TERM-052: crystallized argument
- design-rationale
- epistemology
Oct 06, 2026
LIT-755: A Process-Oriented Approach to Design Rationale
- design-rationale
Oct 06, 2026
LIT-756: Formality Considered Harmful: Experiences, Emerging Themes, and Directions on the Use of Formal Representations in Interactive Systems
- design-rationale
Oct 06, 2026
LIT-757: Groupware and social dynamics: eight challenges for developers
- design-rationale
Oct 06, 2026
LIT-758: Issues as Elements of Information Systems
- design-rationale
Oct 06, 2026
LIT-759: Why CSCW applications fail: problems in the design and evaluation of organizational interfaces
- design-rationale
Oct 06, 2026
LIT-760: Design rationale systems: understanding the issues
- design-rationale
Oct 06, 2026
LIT-761: Argumentation-based design rationale: what use at what cost?
- design-rationale
Oct 06, 2026
LIT-762: gIBIS: a hypertext tool for exploratory policy discussion
- design-rationale
Oct 06, 2026
LIT-763: Questions, Options, and Criteria: Elements of Design Space Analysis
- design-rationale

Created with Quartz v5.0.0 © 2026

Repository
Quartz