Rulealize Registry Find a name /

Rule sets / SignedRequest

rule set · composite

Rulealize.RuleSet.SignedRequest

A request that may not be granted until enough people have signed it. A Rulealize rule set, composed of two others.

What 1.1.0 is made of

this documentSignedRequest1.1.0
usesas req · ^1.1RequestRulealize.RuleSet.Requestas sigs · ^1.1SignaturesRulealize.RuleSet.Signatures
requires — this document's ownstateRulealize.Plugin.State^1.0cmpRulealize.Plugin.Comparison^1.0recRulealize.Plugin.Record^1.0logicRulealize.Plugin.Logic^1.0

Hold it

A document that holds this one writes, in its uses:

"uses": [
  { "ruleSet": "Rulealize.RuleSet.SignedRequest",
    "version": "^1.1", "as": "signedrequest" }
]

as is not optional here. The identifier is the package identifier, so nothing has to look it up; as is the short name the holding document calls it by, and it is what qualifies this rule set's inputs inside that one. An alias defaults to the identifier and may not contain a ., so leaving it out is refused with a message about a key you did not write.

Getting what a uses names is the feed's job rather than this index's. rulealize restore does it from 0.8.0 — the whole graph, into the folder the holding document resolves its components from — and takes the lowest version satisfying every constraint that named it, which is the rule a requires is resolved by.

Inputs a composite could constrain

InputComes from
req.denyRulealize.RuleSet.Request · as req
req.grantRulealize.RuleSet.Request · as req
req.raiseRulealize.RuleSet.Request · as req
sigs.declineRulealize.RuleSet.Signatures · as sigs
sigs.signRulealize.RuleSet.Signatures · as sigs

Releases

  1. 1.1.0 latest

    holds

    requires

  2. 1.0.0

    holds

    requires