Skip to content

Commit

Permalink
improve docs organization
Browse files Browse the repository at this point in the history
  • Loading branch information
@countvajhula
countvajhula committed Sep 20, 2023
1 parent 87b896b commit ba09048
Show file tree
Hide file tree
Showing 2 changed files with 49 additions and 26 deletions.
73 changes: 48 additions & 25 deletions dia-docs/for-congress.scrbl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,9 @@

@section{Attribution}

@subsection[#:style 'unnumbered]{1 Analyze}
@subsection{Analyze}

@subsubsection[#:tag "analyze:consider"]{Consider}

@itemlist[
#:style 'ordered
Expand All @@ -21,7 +23,7 @@

]

@subsection[#:style 'unnumbered]{2 Agree on Analysis}
@subsubsection[#:tag "analyze:agree"]{Agree}

@itemlist[
#:style 'ordered
Expand All @@ -34,20 +36,9 @@

]

@subsection[#:style 'unnumbered]{3 Identify Antecedents}

@itemlist[
#:style 'ordered

@item{As a group, annotate each @emph{leaf} idea in the agreed-upon ideas tree with any projects that you can think of, that is, projects exhibiting that idea or a similar idea. These projects need not have any other relationship to the present project besides common ideas, and these should be recorded with no consideration to temporality (i.e. whether the project came before or after the present one). Projects may appear on any number of leaf ideas.}

@item{Identify projects in the annotated ideas tree that were announced within a year (on either side) of the present project, and write those down as a list of identified "cognates," retaining them on the annotated ideas tree. These will be treated in the same way as true antecedents.}

@item{Identify projects in the annotated ideas tree that were announced more than a year after the present project, and write those down as a list of identified "subsequents," removing them from the annotated ideas tree.}
@subsection{Appraise}

]

@subsection[#:style 'unnumbered]{4 Appraise}
@subsubsection[#:tag "appraise:consider"]{Consider}

@itemlist[
#:style 'ordered
Expand All @@ -62,7 +53,7 @@

]

@subsection[#:style 'unnumbered]{5 Agree on Appraisals}
@subsubsection[#:tag "appraise:agree"]{Agree}

@itemlist[
#:style 'ordered
Expand All @@ -75,34 +66,66 @@

]

@subsection[#:style 'unnumbered]{6 Reconcile the Appraisals}
@subsection{Antecedents}

Discuss to assign weights to each appraisal tree. Consider using the 1-N-N² rule -- that is, if labor is worth K, then capital is worth 1/N × K, and ideas are worth 1/N² × K, for some "scaling factor" N that you agree on. The rationale is that we want labor, capital and ideas to be equally valuable when aggregated over all projects. Since labor is the least portable while ideas are the most portable, this rule models the fluidity of these categories as, roughly, "for every project you directly work on, N projects will use your work, and N² projects will be inspired by it." Note, nevertheless, that the ideas analysis described elsewhere in this document is not in terms of "inspiration" (implying causation) but only similarity.

@subsection[#:style 'unnumbered]{7 Deanonymize and Tally}
@subsubsection[#:tag "antecedents:consider"]{Consider}

@itemlist[
#:style 'ordered

@item{"Deanonymize" – connect each leaf node in the appraised labor tree to a single contributor in the original non-anonymous list prepared by core project contributors.}
@item{On your own, annotate each @emph{leaf} idea in the agreed-upon ideas tree with any projects that you can think of, that is, projects exhibiting that idea or a similar idea. These projects need not have any other relationship to the present project besides common ideas, and these should be recorded with no consideration to temporality (i.e. whether the project came before or after the present one). Projects may appear on any number of leaf ideas.}

@item{Repeat (1) for capital.}
@item{Identify projects in the annotated ideas tree that were announced within a year (on either side) of the present project, and write those down as a list of identified "cognates," retaining them on the annotated ideas tree. These will be treated in the same way as true antecedents.}

@item{Sum up the proportions by leaf nodes across all appraisal trees, weighted by the scaling factor for each tree (i.e. in the manner decided upon in "reconcile the appraisals"), to arrive at the final attributive proportions that total to 100%. Deliver this as an abe/ATTRIBUTIONS.txt file in the project repository.}
@item{Identify projects in the annotated ideas tree that were announced more than a year after the present project, and write those down as a list of identified "subsequents," removing them from the annotated ideas tree.}
]

@subsubsection[#:tag "antecedents:agree"]{Agree}

@itemlist[
#:style 'ordered

@item{Deliver the list of cognates and subsequents as abe/cognates.txt and abe/subsequents.txt, respectively, to be committed to the project repository.}
@item{As a group, reconcile all reported antecedents in the ideas tree, and finalize the list of cognates and subsequents.}

]

@section{Pricing and Valuation}

@subsection[#:tag "evaluate:consider"]{Consider}

@itemlist[
#:style 'ordered

@item{Review the cost analysis and proxy analysis provided by the project.}
@item{On your own, review the cost analysis and proxy analysis provided by the project.}

@item{Come up with a fair market price for use of the project.}

@item{Come up with a valuation of everything created so far in the project.}

]

@subsection[#:tag "evaluate:agree"]{Agree}

@itemlist[
#:style 'ordered

@item{Discuss and agree on price and valuation.}
]

@section{Results}

@subsection{Reconcile the Appraisals}

Discuss to assign weights to each appraisal tree. Consider using the 1-N-N² rule -- that is, if labor is worth K, then capital is worth 1/N × K, and ideas are worth 1/N² × K, for some "scaling factor" N that you agree on. The rationale is that we want labor, capital and ideas to be equally valuable when aggregated over all projects. Since labor is the least portable while ideas are the most portable, this rule models the fluidity of these categories as, roughly, "for every project you directly work on, N projects will use your work, and N² projects will be inspired by it." Note, nevertheless, that the ideas analysis described elsewhere in this document is not in terms of "inspiration" (implying causation) but only similarity.

@subsection{Deanonymize and Tally}

@itemlist[
#:style 'ordered

@item{"Deanonymize" – connect each leaf node in the appraised labor tree to a single contributor in the original non-anonymous list prepared by core project contributors.}

@item{Repeat (1) for capital.}

@item{Sum up the proportions by leaf nodes across all appraisal trees, weighted by the scaling factor for each tree (i.e. in the manner decided upon in "reconcile the appraisals"), to arrive at the final attributive proportions that total to 100%. Deliver this as an abe/ATTRIBUTIONS.txt file in the project repository.}
]
2 changes: 1 addition & 1 deletion dia-docs/for-project.scrbl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

@table-of-contents[]

@section{List contributions}
@section{List all contributions}

@itemlist[
#:style 'ordered
Expand Down

0 comments on commit ba09048

Please sign in to comment.