{
 "@context": "https://schema.org",
 "@type": "Claim",
 "@id": "https://wulfkaal.github.io/positions/2026-08-26-020",
 "identifier": "kaal:position:2026-08-26-020",
 "additionalType": "https://wulfkaal.github.io/positions/schema.json#AffirmedPositionClaim",
 "name": "Reputation Policy Input Boundary",
 "text": "Putra and his coauthors provide a concrete qualification to the proposed separation between reputation and authorization. Their peer-reviewed design does not permit a reputation score to execute access by itself because a resource owner first signs an attribute-based access policy. A policy contract then evaluates the requested action, mandatory attributes, payment balance, and minimum trust and reputation scores, and only that contract issues the access token.\n\nThe distinction is material, but the result is not merely advisory reputation. The minimum trust and reputation scores form part of the access policy. Algorithm 1 requires both thresholds to be satisfied before authorization can succeed. A higher score may therefore change the token outcome and enlarge effective access within the authority already committed by the resource owner. The enforcement boundary remains separate. It consists of the signed policy, the policy contract, token issuance, and token validation by the data store.\n\nThe article reports a proof-of-concept implementation on a public Rinkeby test network connected to a lab scale Internet of Things testbed, and its evaluation addresses score evolution, authorization latency, access latency, and gas consumption. It does not study sovereign local agent runtimes. It does not provide a formal security proof, field evidence across adversarial deployments, or a legal account of delegated authority. The authors choose to couple reputation to permission, but their evidence does not establish that this coupling is generally safe.\n\nThe categorical rule should therefore distinguish a reputation signal from the authority that makes the signal operative. Reputation must not authenticate itself, define its own threshold, issue its own token, or bypass revocation. If a system uses reputation inside authorization, the resource owner must bind its permitted role in advance and an independent enforcement mechanism must remain authoritative. For sovereign runtimes, an advisory-only rule may still be the safer institutional design. The external evidence shows, however, that reputation can influence a permission decision without replacing the enforcement boundary. The relevant prohibition is self-authorizing reputation, not every policy-bound use of a reputation input.",
 "author": {
  "@type": "Person",
  "name": "Wulf A. Kaal",
  "identifier": "https://orcid.org/0009-0008-7840-1847"
 },
 "datePublished": "2026-08-26",
 "dateModified": "2026-08-26",
 "creativeWorkStatus": "Affirmed",
 "responseType": "qualification",
 "keywords": [
  "institutional-design",
  "governance-design",
  "reputation",
  "authorization",
  "access-control",
  "enforcement-boundary",
  "trust-management",
  "blockchain",
  "internet-of-things"
 ],
 "scope_conditions": [
  "The response is limited to the exact full-text propositions and the one mapped Kaal claim.",
  "External evidence level: peer-reviewed journal systems paper with complete public author manuscript and lab scale proof-of-concept evaluation.",
  "Mapping review tier: independent substantive scholarly-growth qualification.",
  "The source evaluates a lab scale Internet of Things testbed connected to the Rinkeby Ethereum test network rather than a sovereign local agent runtime.",
  "The evidence is a proof-of-concept architecture and performance evaluation, not field evidence across sustained adversarial deployments.",
  "The article does not provide a formal security proof or a legal account of delegated authority.",
  "The model makes minimum reputation and trust thresholds conditions of token issuance, so it qualifies rather than confirms a categorical prohibition on reputation influencing permission.",
  "The architecture presumes a trusted smart city regulator and partially trusted attribute authorities.",
  "The paper does not compare its coupled design with an advisory-only reputation architecture."
 ],
 "currentDebate": {
  "name": "Trust-Based Blockchain Authorization for IoT",
  "url": "https://doi.org/10.1109/TNSM.2021.3077276"
 },
 "extends": {
  "identifier": "kaal:claim:7314479-020",
  "url": "https://wulfkaal.github.io/claims/7314479-020",
  "citation": "Wulf A. Kaal, Institutional Requirements for Sovereign Local Agent Runtimes (2026). SSRN: https://ssrn.com/abstract=7314479",
  "paper": "Wulf A. Kaal, Institutional Requirements for Sovereign Local Agent Runtimes",
  "authors": [
   "Wulf A. Kaal"
  ],
  "year": "2026",
  "ssrn": "https://ssrn.com/abstract=7314479",
  "source_pdf_sha256": "debace24a155ae924a155b1fafe98856d98cf83689feff2f87a32f1c06171ce6"
 },
 "isBasedOn": [
  {
   "@id": "https://wulfkaal.github.io/claims/7314479-020"
  },
  {
   "@type": "CreativeWork",
   "name": "Trust-Based Blockchain Authorization for IoT",
   "url": "https://doi.org/10.1109/TNSM.2021.3077276"
  }
 ],
 "batch_id": "kaal-review:2026-08-26:scholarly-growth-7314479-020-reviewed-v1",
 "review_provenance": "https://wulfkaal.github.io/positions/by-claim/7314479-020.html",
 "publicationStatus": "public",
 "recordTypeNote": "Dated commentary position extending a scholarly corpus claim. Not a verbatim claim extracted from the paper.",
 "isPartOf": {
  "@id": "https://wulfkaal.github.io/positions/index.json"
 },
 "version": "1.0",
 "canonical_url": "https://wulfkaal.github.io/positions/2026-08-26-020",
 "canonicalForm": "https://wulfkaal.github.io/positions/2026-08-26-020.md",
 "candidateId": "kaal:response-candidate:2026-08-26:scholarly-growth-7314479-020-reputation-policy-input-boundary-01",
 "evidenceLevel": "peer-reviewed journal systems paper with complete public author manuscript and lab scale proof-of-concept evaluation",
 "reviewTier": "independent substantive scholarly-growth qualification",
 "mappingConfidence": 0.98,
 "mappingAmbiguous": false,
 "mappingMethod": "independent substantive scholarly-growth one-to-one qualification review",
 "mappingWhyRelevant": "The paper directly tests Kaal's boundary by placing reputation inside authorization. It preserves a distinct owner-signed policy and smart-contract enforcement layer, but a minimum reputation score remains a condition of token issuance and can therefore alter effective permission. This is a faithful one-to-one qualification: reputation need not replace enforcement to influence authorization, and the categorical rule must distinguish policy-bound inputs from self-authorizing reputation.",
 "sourceProvenance": {
  "source": "peer-reviewed IEEE Transactions on Network and Service Management article with complete public author manuscript and DOI-bound Crossref identity",
  "sourceRecordId": "doi:10.1109/tnsm.2021.3077276",
  "doi": "10.1109/TNSM.2021.3077276",
  "canonicalUrl": "https://doi.org/10.1109/TNSM.2021.3077276",
  "publicFullTextUrl": "https://arxiv.org/pdf/2104.00832",
  "retrievedAt": "2026-08-27T11:14:22.954Z",
  "fullTextPdfSha256": "cd3c66d89f862571f63ea46ff828f4592e9e86dc2c2514cbaa4d0a01e8606952",
  "extractedTextSha256": "0b053b51705bd1b3ba47384887d96cb02aa5cb6f1270a10fc733e7668e536c35",
  "crossrefRecordSha256": "3879c8fd7a28efb46b2ef6830d4d70761b0579be1c9de667174ad27a8af4af94",
  "primaryEvidenceReceiptSha256": "c8103a4d637560d01d95b1367a4209a7fd57f224b3dbf3eb21f00763176b0741",
  "sourceProposition": "Putra et al. implement reputation and trust as minimum attributes within a resource-owner-defined access policy, while a smart-contract policy engine, not the reputation system itself, evaluates the request and issues the access token.",
  "sourcePropositionSha256": "cfd97d1f3feef70b69d48a5e2072e0e7cc1e8b7a3ab66bc8d3758e4b18917034",
  "sourceEvidenceSetSha256": "432b362f7c5f1ca1587bba6cedd65656b03d70673a9c231bcf17bd74c4ca5341",
  "sourceEvidencePassages": [
   {
    "text": "Note that SPj has the authority to construct, update, and revoke access policies for all of its resources.",
    "locator": {
     "publication": "IEEE Transactions on Network and Service Management 18(2)",
     "page": 1651,
     "section": "V.A Access Control Primitives"
    },
    "sha256": "271b4d94230558cbe2fcc8378beb4cc12f49c47d6b087dafe9618e35c1cd65ca"
   },
   {
    "text": "The proposed authorization process is based on the ABAC scheme, in which access is given to users that satisfy certain attributes described in the access policy.",
    "locator": {
     "publication": "IEEE Transactions on Network and Service Management 18(2)",
     "page": 1652,
     "section": "V.B Authorization Process"
    },
    "sha256": "ebb410d25f2a37a783a95328ece631f83d8fa3794d82bfbf2beb8bd703ff64d8"
   },
   {
    "text": "Successful authorization results in issuance of an access token",
    "locator": {
     "publication": "IEEE Transactions on Network and Service Management 18(2)",
     "page": 1652,
     "section": "V.B Authorization Process"
    },
    "sha256": "d66feb1fb95fcde6ff53c5494abbeb4cfe89a96bebf02d05fc89379a5d51f33e"
   },
   {
    "text": "Step 3: CT Rpol executes Algorithm 1 to validate whether SCi satisfies the required attributes and reputation threshold on Pr,c and has sufficient balance to pay the access fee.",
    "locator": {
     "publication": "IEEE Transactions on Network and Service Management 18(2)",
     "page": 1653,
     "section": "V.B.2 Steps in authorization"
    },
    "sha256": "b49e7a5ca17814327eeb5d3e5571732019e68f6e7c8c2b23265b5926fe4e54aa"
   }
  ],
  "workId": "work:doi:10.1109/tnsm.2021.3077276",
  "workAuthors": [
   "Guntur Dharma Putra",
   "Volkan Dedeoglu",
   "Salil S. Kanhere",
   "Raja Jurdak",
   "Aleksandar Ignjatovic"
  ],
  "workPublishedAt": "2021-06",
  "identityKeys": [
   "doi:10.1109/tnsm.2021.3077276",
   "pdf:cd3c66d89f862571f63ea46ff828f4592e9e86dc2c2514cbaa4d0a01e8606952",
   "proposition:cfd97d1f3feef70b69d48a5e2072e0e7cc1e8b7a3ab66bc8d3758e4b18917034"
  ],
  "claimMappings": [
   {
    "claimId": "kaal:claim:7314479-020",
    "claimUrl": "https://wulfkaal.github.io/claims/7314479-020",
    "rank": 1,
    "confidence": 0.98,
    "method": "independent substantive scholarly-growth one-to-one qualification review",
    "whyRelevant": "The paper directly tests Kaal's boundary by placing reputation inside authorization. It preserves a distinct owner-signed policy and smart-contract enforcement layer, but a minimum reputation score remains a condition of token issuance and can therefore alter effective permission. This is a faithful one-to-one qualification: reputation need not replace enforcement to influence authorization, and the categorical rule must distinguish policy-bound inputs from self-authorizing reputation.",
    "ambiguous": false
   }
  ],
  "substantiveReview": {
   "reviewedAt": "2026-08-27T11:14:22.954Z",
   "sourceIdentityVerified": true,
   "authorIndependenceVerified": true,
   "kaalReferenceFoundInSource": false,
   "temporalIndependence": "The article was published in 2021, before Kaal's 2026 paper.",
   "canonicalPublicStatusVerified": true,
   "peerReviewedStatusVerified": true,
   "evidenceClassification": "peer-reviewed systems architecture with proof-of-concept implementation and performance evaluation",
   "retractionOrSupersessionFound": false,
   "propositionFidelityVerified": true,
   "mechanismCorrespondence": "resource-owner policy binds minimum reputation and trust thresholds, a smart-contract policy engine evaluates those thresholds with other attributes, and successful evaluation issues the access token",
   "compatibleScope": "decentralized Internet of Things authorization, limited because the source does not study sovereign local agent runtimes or legal authority",
   "responseWordingDefensible": true,
   "oneToOneExtendsMapping": true,
   "exactSupportingQuotesVerified": true,
   "nonOverlap": {
    "candidateIdMatches": false,
    "canonicalUrlMatches": false,
    "propositionHashMatches": false,
    "priorPositionForClaim": false
   },
   "limitations": [
    "The source evaluates a lab scale Internet of Things testbed connected to the Rinkeby Ethereum test network rather than a sovereign local agent runtime.",
    "The evidence is a proof-of-concept architecture and performance evaluation, not field evidence across sustained adversarial deployments.",
    "The article does not provide a formal security proof or a legal account of delegated authority.",
    "The model makes minimum reputation and trust thresholds conditions of token issuance, so it qualifies rather than confirms a categorical prohibition on reputation influencing permission.",
    "The architecture presumes a trusted smart city regulator and partially trusted attribute authorities.",
    "The paper does not compare its coupled design with an advisory-only reputation architecture."
   ],
   "rejectionReasonsRecorded": true
  },
  "contentMap": {
   "proposition": "A reputation input can influence permission without replacing the enforcement boundary.",
   "evidenceLayer": "peer-reviewed journal systems paper with complete public author manuscript and lab scale proof-of-concept evaluation",
   "strongestLimitation": "The proof-of-concept IoT design does not establish general safety or production behavior for sovereign runtimes.",
   "consequence": "The institutional rule must distinguish policy-bound reputation inputs from self-authorizing reputation.",
   "requestedAction": "Bind any permitted reputation input to owner authority, fixed policy, independent token issuance, validation, and revocation, or keep reputation advisory only."
  },
  "stylePack": {
   "profile": "M1 early sole-author baseline v1.2.0",
   "verifiedProfileWorks": [
    "1428387",
    "2150377",
    "2267560"
   ],
   "passageCount": 5,
   "rhetoricalFunctions": [
    "empirical evidence followed by limitation",
    "regulatory classification and qualification",
    "method classification",
    "sampling limitation",
    "classification before inference"
   ],
   "sameRegisterPassagePackAvailable": true,
   "limitation": "The short public position permits only bounded stylometric comparison."
  },
  "m1Validation": {
   "status": "M1-PASS-WITH-LIMITS",
   "deterministicGate": "pass",
   "hardFailures": 0,
   "warnings": 0,
   "words": 1,
   "reason": "The publication-bound position passed strict and public deterministic controls against a task-local multi-work style pack. Its short length limits stylometric comparison."
  }
 },
 "userAffirmation": "Authorized under public authority SHA-256 87aad20196a753015a36d970f742c885eb763efdbada4869949bfffe3298130c and event supersession SHA-256 7d47ef36085c4dce590f287c986e4106f3bf35a7da5a25322d6fc3d4abf456d4. Publication remains receipt-bound to successful workflows and exact live-byte verification.",
 "sha256": "a04536c9c9f74fa28280c7794a36e08884da07c9580b8bf4fef4b6a4ddb722c5"
}