Oraclizer · jay-oraclizer · Aug 1, 2026 · Aug 1, 2026
@@ -0,0 +1,6 @@
+# Public profile, policy, automation, and metadata ownership
+* @jay-oraclizer
+
+/profile/ @jay-oraclizer
+/.github/ @jay-oraclizer
+/scripts/ @jay-oraclizer
@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/Oraclizer/.github/blob/main/SECURITY.md
+    about: Use the affected repository's private vulnerability-reporting path.
+  - name: Support boundary
+    url: https://github.com/Oraclizer/.github/blob/main/SUPPORT.md
+    about: Review supported and unsupported request channels.
@@ -0,0 +1,46 @@
+name: Documentation correction
+description: Report a public documentation, link, accessibility, or rendering defect.
+title: "[Docs]: "
+labels:
+  - documentation
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for helping improve Oraclizer's public documentation. Do not include sensitive security details or private repository content.
+  - type: input
+    id: repository
+    attributes:
+      label: Repository or public page
+      description: Identify the affected repository or URL.
+      placeholder: Oraclizer/.github or https://github.com/Oraclizer
+    validations:
+      required: true
+  - type: input
+    id: location
+    attributes:
+      label: Exact location
+      description: Provide the file, section, anchor, or rendered element.
+    validations:
+      required: true
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: Explain what is inaccurate, inaccessible, broken, or unclear.
+    validations:
+      required: true
+  - type: textarea
+    id: correction
+    attributes:
+      label: Proposed correction
+      description: Suggest precise replacement text or behavior if possible.
+    validations:
+      required: false
+  - type: checkboxes
+    id: safety
+    attributes:
+      label: Public-report confirmation
+      options:
+        - label: This report contains no vulnerability details, credentials, personal data, private links, or confidential material.
+          required: true
@@ -0,0 +1,60 @@
+name: Repository surface defect
+description: Report a metadata, status, navigation, Community Profile, or repository-setting defect.
+title: "[Surface]: "
+labels:
+  - repository-surface
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this form for non-sensitive public repository-surface problems. Security reports belong in the private path described by SECURITY.md.
+  - type: input
+    id: repository
+    attributes:
+      label: Affected repository
+      placeholder: Oraclizer/.github
+    validations:
+      required: true
+  - type: dropdown
+    id: surface
+    attributes:
+      label: Surface
+      options:
+        - About or Topics
+        - Organization profile
+        - Community Profile
+        - Issue or Pull Request template
+        - Workflow or status check
+        - Branch or merge setting
+        - Social preview
+        - Other public metadata
+    validations:
+      required: true
+  - type: textarea
+    id: observed
+    attributes:
+      label: Observed state
+      description: Include the public URL and exact current behavior.
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected state
+      description: Describe the accurate or intended public behavior.
+    validations:
+      required: true
+  - type: textarea
+    id: evidence
+    attributes:
+      label: Evidence
+      description: Add non-sensitive screenshots, response codes, or references.
+    validations:
+      required: false
+  - type: checkboxes
+    id: safety
+    attributes:
+      label: Public-report confirmation
+      options:
+        - label: This report is non-sensitive and contains no credentials, private repository content, or uncoordinated vulnerability information.
+          required: true
@@ -0,0 +1,26 @@
+## Summary
+
+Describe the smallest reviewable change and link the issue when applicable.
+
+## Public-surface impact
+
+- [ ] Organization profile or navigation
+- [ ] Repository metadata or social preview
+- [ ] Community-health default or contribution route
+- [ ] Workflow, ruleset, or repository setting
+- [ ] No protocol, proof, implementation, audit, release, or deployment claim changes
+
+Explain any affected status or assurance boundary:
+
+## Verification
+
+- [ ] `node scripts/verify-profile.mjs`
+- [ ] `git diff --check`
+- [ ] Changed links resolve or an automated-access limitation is recorded
+- [ ] Desktop and mobile rendering checked when profile markup or assets change
+- [ ] No credentials, private links, internal planning data, or machine-local paths
+
+## Reviewer focus
+
+Identify the wording, status boundary, rendering detail, or repository setting
+that deserves the closest review.
@@ -0,0 +1,12 @@
+version: 2
+updates:
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 5
+    labels:
+      - dependencies
+      - github-actions
+    commit-message:
+      prefix: chore(actions)
@@ -0,0 +1,29 @@
+name: Repository health
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: repository-health-${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  profile-health:
+    name: Profile health
+    runs-on: ubuntu-24.04
+    timeout-minutes: 5
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
+
+      - name: Verify public repository surface
+        run: node scripts/verify-profile.mjs
@@ -0,0 +1,43 @@
+# Code of Conduct
+
+## Our commitment
+
+Oraclizer is committed to a respectful, harassment-free environment for
+technical, academic, standards, and community participation.
+
+## Expected behavior
+
+- Challenge claims, proofs, assumptions, and designs with technical specificity.
+- Distinguish people from the work under review.
+- Accept correction and take responsibility for mistakes.
+- Respect disclosure, confidentiality, attribution, and citation boundaries.
+- Use inclusive language and make participation accessible where practical.
+- Focus discussion on rigorous, reproducible, and constructive outcomes.
+
+## Unacceptable behavior
+
+- Harassment, threats, insults, discriminatory comments, or sexualized conduct.
+- Trolling, sustained disruption, or bad-faith misrepresentation.
+- Publishing private information or vulnerability details without permission.
+- Retaliation against a good-faith counterexample or security report.
+- Plagiarism, fabricated evidence, or deliberate removal of attribution.
+
+## Enforcement
+
+Report conduct concerns privately to `jay@oraclizer.io` with the subject
+`ORACLIZER CONDUCT`. Reports will be handled as confidentially as reasonably
+possible. Maintainers may edit or remove content, close or lock interactions,
+reject contributions, or restrict participation.
+
+Enforcement should be proportionate and separate from whether a participant's
+technical criticism is correct.
+
+## Scope
+
+This policy applies in Oraclizer-managed repository spaces and when someone
+officially represents Oraclizer in public. It does not govern independent
+academic, technical, or standards criticism made without project
+representation.
+
+This policy is adapted from the Contributor Covenant, version 2.1:
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
@@ -0,0 +1,51 @@
+# Contributing
+
+This file provides fallback contribution guidance for Oraclizer repositories
+that do not define their own `CONTRIBUTING.md`. Repository-specific guidance
+and licenses take precedence.
+
+## Choose the right channel
+
+| Contribution | Channel |
+| --- | --- |
+| Broken link, rendering defect, accessibility problem, or documentation correction | Documentation issue form |
+| Repository metadata, public-status, or navigation defect | Repository-surface issue form |
+| Material protocol, proof, architecture, or public-claim change | Issue first, before a Pull Request |
+| Sensitive or potentially exploitable concern | Private path in `SECURITY.md` |
+| Usage or support request | Boundary and routing in `SUPPORT.md` |
+
+Search existing issues before opening a new one. Keep each issue or Pull
+Request to one reviewable concern.
+
+## Pull Request expectations
+
+A Pull Request should:
+
+- explain what changed, why it changed, and which public surface is affected;
+- link the review issue when the change is material or claim-affecting;
+- distinguish research, specification, implementation, audit, release, and
+  deployment status;
+- include the smallest relevant verification result;
+- preserve accessibility, relative links, and responsive rendering;
+- contain no credentials, private correspondence, internal planning data,
+  machine-local paths, generated logs, or unrelated artifacts;
+- use the private reporting path for sensitive concerns.
+
+For this `.github` repository, run:
+
+```bash
+node scripts/verify-profile.mjs
+```
+
+The check validates repository structure and public-surface invariants. It is
+not a substitute for proof, code, deployment, security, or legal review.
+
+## Contribution rights
+
+By contributing to this `.github` repository, you represent that you have the
+right to submit the material and agree that it may be distributed under the
+BSD 3-Clause License. Contributions to another Oraclizer repository remain
+subject to that repository's license and contribution policy.
+
+Opening an issue or Pull Request creates no obligation to accept, merge,
+publish, release, or respond within a particular period.
@@ -0,0 +1,56 @@
+# Governance
+
+This document governs the public `Oraclizer/.github` repository and the
+organization-profile surface it renders. It is not a governance document for
+an external protocol, standards body, deployed network, or asset.
+
+## Maintainer authority
+
+Oraclizer maintains this repository. Jay Kim (`@jay-oraclizer`) is the current
+repository owner and review owner. The maintainer controls access, triage,
+merge decisions, public-profile claims, repository settings, and security
+coordination.
+
+Opening an issue or Pull Request creates no obligation to accept, merge,
+publish, release, or respond within a particular period.
+
+## Decision principles
+
+Changes are evaluated for:
+
+1. factual consistency with public repositories, specifications, papers, and
+   standards-process state;
+2. explicit separation of research, specification, implementation, audit,
+   release, and deployment status;
+3. accessibility, stable navigation, and responsive rendering;
+4. licensing, attribution, disclosure, and confidentiality boundaries;
+5. reproducibility of the repository-health check;
+6. minimal, reviewable history through Pull Requests.
+
+## Merge policy
+
+Changes use a topic branch and Pull Request. The repository-health workflow
+must pass, review conversations must be resolved, and the default branch must
+retain a linear history. Force pushes and deletion of the default branch are
+not permitted.
+
+A passing check validates repository structure only. It does not establish
+the correctness or readiness of any project described by the profile.
+
+## Tags and releases
+
+This repository is an organization profile and policy surface, not a packaged
+or deployable software product. It therefore does not create routine version
+tags or GitHub Releases merely to mark documentation updates.
+
+If this repository later distributes a versioned artifact, a tag and release
+must identify an immutable commit, artifact scope, status, verification, and
+change summary. Existing tags must never be moved or reused.
+
+Visibility changes, protocol versions, paper publication, standards review,
+audits, deployments, tags, and releases remain separate decisions.
+
+## Amendments
+
+Governance changes use the same Pull Request and review path and remain
+traceable in Git history.
@@ -0,0 +1,29 @@
+BSD 3-Clause License
+
+Copyright (c) 2026, Oraclizer
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its contributors
+   may be used to endorse or promote products derived from this software
+   without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.