PTSIP 0.3.7__tar.gz → 0.3.8a2__tar.gz

ptsip-0.3.8a2/License-Authority/COMMERCIAL-USE.md

@@ -0,0 +1,301 @@
+# PTSIP Commercial Use and Cooperation Procedure
+
+This document defines the current Official Cooperation Channels and submission mechanics for PTSIP Community Reciprocity License 1.0.
+
+**Effective Time:** `2026-09-15T00:00:00Z` (UTC).
+
+It does not add substantive duties beyond LICENSE. If this document conflicts with LICENSE.md, LICENSE.md controls.
+
+## Standing Commercial Authorization
+
+No individual approval response is required.
+
+Standing Commercial Authorization becomes available when a Commercial User:
+
+1. accepts PTSIP Community Reciprocity License 1.0;
+2. expressly accepts both the applicable PTSIP License and the Commercial Cooperation Duty;
+3. identifies the PTSIP Version or Revision actually used; and
+4. submits a valid Commercial Use Registration within 90 calendar days of first Commercial Use; and
+5. continues to comply with the applicable attribution and cooperation duties.
+
+PTSIP does not require a default monetary license fee.
+
+## Official Cooperation Channels
+
+### Public registration, reports, and non-confidential findings
+
+Use the PTSIP GitHub Issues page:
+
+https://github.com/Kinirin/PTSIP/issues
+
+Use one of these title prefixes:
+
+- [License][Commercial Registration]
+- [License][Commercial Report]
+- [License][Final Commercial Report]
+- [License][Research Report]
+- [License][Research Summary]
+- [License][Material Finding]
+
+The GitHub issue timestamp is sufficient evidence of submission.
+
+### PTSIP source changes
+
+Submit source changes through a pull request to:
+
+https://github.com/Kinirin/PTSIP
+
+A pull request, patch link, or equivalent source-form submission may satisfy the PTSIP-modification return requirement when it contains enough information to review and reproduce the PTSIP-specific change.
+
+### Security-sensitive or confidential findings
+
+Do not place credentials, personal data, customer secrets, or other protected information in a public issue.
+
+If the repository exposes a private vulnerability-reporting or other private project channel, use that channel.
+
+If no private channel is available, submit a redacted public Material Finding containing only enough non-confidential information to identify that a finding exists and to request a private follow-up channel. The License never requires public disclosure of protected information.
+
+## Commercial Use Registration template
+
+Title:
+
+[License][Commercial Registration] <organization or project name>
+
+Body:
+
+### User
+Individual or legal entity:
+
+### Commercial activity
+Product, service, system, business activity, or internal commercial function:
+
+### First Commercial Use date
+YYYY-MM-DD:
+
+### PTSIP License version — REQUIRED
+PTSIP Community Reciprocity License version:
+
+### PTSIP version / immutable revision — REQUIRED
+Provide at least one precise identifier. Include both when reasonably available.
+Tool/release version:
+Specification family:
+Immutable Specification revision:
+Git commit or other immutable revision:
+
+### Primary environment
+Relevant coding agents, CI, operating environment, platforms, or integrations:
+
+### Responsible contact
+GitHub account or other accountable project contact:
+
+### Attribution location
+Where PTSIP attribution is or will be provided:
+
+### License and Cooperation Duty acceptance — REQUIRED
+By submitting this Commercial Use Registration, the registering individual or Legal Entity expressly accepts:
+
+1. the PTSIP Community Reciprocity License version identified in this registration; and
+2. the Commercial Cooperation Duty, including the applicable attribution, reporting, Material Finding, PTSIP-modification return, cure, suspension, and reinstatement obligations.
+
+We acknowledge that the Commercial Cooperation Duty is a material and essential condition of Standing Commercial Authorization and is not merely a voluntary recommendation.
+
+Submission of this registration constitutes affirmative acceptance of these terms for the Commercial Use identified above.
+
+## Annual Commercial Cooperation Report template
+
+Title:
+
+[License][Commercial Report] <organization or project name> <reporting period>
+
+Body:
+
+### Reporting period
+Start:
+End:
+
+### PTSIP License version — REQUIRED
+
+### PTSIP versions / immutable revisions used — REQUIRED
+Provide at least one precise identifier for each materially used PTSIP line; include both version and immutable revision when reasonably available.
+
+### Usage scope
+Where and how PTSIP was used.
+
+### Relevant environments and integrations
+Coding agents, CI, platforms, tools, or workflows.
+
+### Compatibility findings
+Successful compatibility, incompatibilities, and required workarounds.
+
+### Policy and architecture findings
+Ambiguous, incomplete, unexpectedly strict, unexpectedly permissive, or difficult-to-apply PTSIP policy behavior.
+
+### Verification and failure findings
+Known false positives, false negatives, incorrect decisions, failure patterns, or bypasses.
+
+### Improvements
+Concrete suggestions, missing capabilities, usability problems, or interoperability improvements.
+
+### PTSIP modifications
+Describe PTSIP-specific modifications and link the corresponding PR, patch, or technical contribution. State "none" only if none were made.
+
+### Operational observations
+Shareable aggregated findings that may help improve PTSIP. This may include agent behavior, compatibility matrices, evaluation results, or measured context, reasoning, token, credit, or development-cost observations.
+
+### Protected information
+Identify any categories omitted because they could not lawfully or reasonably be disclosed. Do not include the protected information itself.
+
+### Attestation
+To the best of our knowledge, this report is a truthful account of material PTSIP-related knowledge reasonably obtained during the reporting period.
+
+## Final Commercial Cooperation Report
+
+Use the annual report template and add:
+
+### Commercial Use end date
+
+### Reason use ended
+
+### Remaining deployed or maintained PTSIP-related material
+Explain whether any PTSIP or PTSIP-Derived Material continues to materially enable the commercial activity.
+
+### Outstanding obligations
+List any Material Finding or PTSIP modification submission that is still being completed.
+
+## Research Cooperation Report template
+
+Title:
+
+[License][Research Report] <organization or project> <reporting period>
+
+Body:
+
+### Research purpose
+
+### Research period
+
+### PTSIP License version — REQUIRED
+
+### PTSIP versions / immutable revisions — REQUIRED
+Provide at least one precise identifier; include both when reasonably available.
+
+### Research environment and integrations
+
+### Compatibility observations
+
+### Policy or architecture observations
+
+### Failures or unexpected behavior
+
+### PTSIP modifications
+
+### Improvement suggestions
+
+### Publications or presentations
+Links if public and available.
+
+### Protected information
+Identify only the category of information omitted; do not disclose protected content.
+
+## Research Cooperation Summary template
+
+Title:
+
+[License][Research Summary] <organization or project>
+
+Body:
+
+### Research purpose and outcome
+
+### PTSIP License version — REQUIRED
+
+### PTSIP versions / immutable revisions — REQUIRED
+Provide at least one precise identifier; include both when reasonably available.
+
+### Duration of material PTSIP use
+
+### Most useful PTSIP behavior
+
+### Most limiting or unclear PTSIP behavior
+
+### Compatibility findings
+
+### Material findings already reported
+Links:
+
+### PTSIP modifications or improvements returned
+Links:
+
+### Publication, presentation, or report
+Link if public and available.
+
+## Material Finding template
+
+Title:
+
+[License][Material Finding] <short description>
+
+Body:
+
+### PTSIP License version — REQUIRED
+
+### PTSIP version / immutable revision — REQUIRED
+Provide at least one precise identifier; include both when reasonably available.
+
+### Finding category
+Policy ambiguity / false positive / false negative / compatibility / agent behavior / conformance / security / other
+
+### Summary
+
+### Expected behavior
+
+### Observed behavior
+
+### Reproduction information
+Provide only non-confidential information.
+
+### Impact
+
+### Workaround, if known
+
+### Related PTSIP modification, if any
+
+## Compliance timing principle
+
+The compliance periods in the PTSIP License are intended to encourage voluntary cooperation and reasonable correction, not to create traps for users acting in good faith.
+
+A missed ordinary deadline begins the cure process defined in LICENSE rather than being treated as a reason for immediate punitive action.
+
+## Reporting anniversary
+
+The normal commercial reporting anniversary is based on the first Commercial Use date stated in the registration.
+
+Example:
+
+First Commercial Use: 2026-10-15
+First annual reporting period ends: 2027-10-14
+First report due: 2028-01-12
+
+A correction, late report, suspension, or automatic reinstatement does not reset that anniversary unless the applicable License or a later written agreement expressly says otherwise.
+
+## Updating a registration
+
+A new registration is not required for every internal change.
+
+Update or add a registration when Commercial Use changes materially, such as:
+
+- a materially different product or service;
+- a materially different legal entity;
+- a move from research-only use into Commercial Use;
+- resumed Commercial Use after a real end of use;
+- a materially different commercial use category not reasonably covered by the existing record.
+
+Minor product renames, team changes, routine version upgrades, or ordinary technical refactoring do not by themselves require a new registration.
+
+## No profit statement required
+
+PTSIP does not ask Commercial Users to prove profit, revenue, or PTSIP-attributable financial return.
+
+The duty follows Commercial Use, not profitability.
+
+A report may state that a metric was not measured. That does not remove the obligation to provide other reasonably available PTSIP-related knowledge.

ptsip-0.3.8a2/License-Authority/LICENSE-GUIDE.md

@@ -0,0 +1,159 @@
+# PTSIP License Guide
+
+This guide explains PTSIP Community Reciprocity License 1.0 in plain language.
+
+**Effective Time:** `2026-09-15T00:00:00Z` (UTC). It is not a substitute for LICENSE.md. If this guide conflicts with LICENSE.md, LICENSE.md controls.
+
+## Core philosophy
+
+> PTSIP does not require contribution as a price for access. PTSIP requires reciprocity so that knowledge gained through PTSIP does not become a one-way private benefit.
+
+PTSIP is publicly available because the project is intended to be inspected, used, tested, improved, and shared. The license is not designed primarily to collect money. It is designed to preserve original authorship and to make organized or commercial users return useful PTSIP-related knowledge and improvements when they obtain them.
+
+This is a source-available community reciprocity license. It is not an OSI-approved Open Source license.
+
+## Quick guide
+
+| Use | Allowed? | Main duties |
+| --- | --- | --- |
+| Personal private, noncommercial use | Yes | Keep notices in copies; no registration or periodic report |
+| Public noncommercial redistribution | Yes | Attribution; keep PTSIP-derived portions under this license |
+| Modified PTSIP distribution | Yes | Attribution; make the PTSIP-derived source available under this license |
+| Educational use | Yes | Attribution; institutional long-term use follows research reciprocity |
+| Institutional or company research | Yes | Attribution; annual lightweight report after 12 months; Material Findings shared |
+| Commercial development before revenue | Yes | Commercial registration and cooperation duties apply |
+| Commercial use with zero revenue or operating loss | Yes | Same commercial duties; profit is not the trigger |
+| Internal company use that saves time, AI credits, or development cost | Yes | Commercial duties when used for a business purpose |
+| Competing product | Yes | Attribution if PTSIP material is used; commercial reciprocity if used commercially |
+| AI training or agent development | Yes | Attribution plus research or commercial reciprocity as applicable |
+| Independent implementation of a similar idea without copying PTSIP expression | Not restricted by this license solely because of similarity | Do not falsely claim PTSIP authorship or official status |
+
+## What counts as Commercial Use?
+
+Commercial Use is based on purpose, not accounting results.
+
+It includes use intended to develop, operate, support, improve, market, sell, or materially enable a business activity. Revenue does not need to exist.
+
+Examples that remain Commercial Use:
+
+- a paid product that has not launched yet;
+- a startup product with zero revenue;
+- a product or company operating at a loss;
+- a free beta intended to become a business;
+- an advertising-supported or customer-acquisition service;
+- internal use that reduces development cost, context use, reasoning cost, token use, or coding-agent credits;
+- consulting or client work;
+- an investment-funded commercial development project.
+
+A company does not avoid cooperation duties by saying that it cannot measure how much profit came from PTSIP.
+
+## Research can be long or short
+
+PTSIP does not require a project to predict when research will end.
+
+Institutional Research Use:
+
+- requires attribution;
+- requires an annual Research Cooperation Report only after use continues for more than 12 months;
+- requires a Research Cooperation Summary when material research ends or is first materially published if the same period has not already been substantially reported;
+- requires Material Findings to be shared within the period defined in LICENSE.
+
+If a research project later becomes a commercial development effort, commercial duties begin when the Commercial Purpose begins. Earlier research duties do not disappear.
+
+## What must be shared?
+
+PTSIP asks for PTSIP-related knowledge, not unrelated company secrets.
+
+Useful reciprocity may include:
+
+- compatibility results;
+- coding-agent behavior findings;
+- policy ambiguities;
+- false positives and false negatives;
+- failure patterns;
+- test or evaluation results;
+- reproducible examples;
+- anonymized or aggregated usage observations;
+- documentation corrections;
+- architecture or policy proposals;
+- PTSIP patches and modifications.
+
+The license does not require disclosure of unrelated proprietary product code, customer-confidential information, credentials, personal information, or unrelated trade secrets.
+
+## What if nothing went wrong?
+
+You are not required to invent defects or send meaningless patches.
+
+A valid report may truthfully say that no material defect was found. It must still identify the real use context, PTSIP version, relevant environment, integrations, and other required information that is reasonably available.
+
+The purpose is to return actual knowledge gained through use.
+
+## Code reuse and PTSIP architecture
+
+The license protects copyrightable PTSIP expression rather than claiming ownership of every similar software idea.
+
+Protected material includes PTSIP-specific code, Specification text, schemas, policy definitions, rule identifiers, conformance vectors, documentation, and copyrightable selection or arrangement.
+
+Examples likely to remain PTSIP-derived when PTSIP material was used as the source include:
+
+- porting PTSIP code from Python to another language;
+- translating PTSIP normative text into a machine contract;
+- copying PTSIP schemas and renaming fields;
+- using PTSIP source or Specification as input to an AI system and distributing the transformed implementation;
+- reproducing a substantial distinctive arrangement of PTSIP-specific protected material.
+
+A separately created implementation is not automatically PTSIP-derived merely because it independently reaches a similar general architecture or method.
+
+There is therefore no fragile list of specific module paths that must be updated whenever PTSIP is refactored.
+
+## Standing Commercial Authorization
+
+Commercial users do not need to wait for individual approval.
+
+A commercial user receives Standing Commercial Authorization by:
+
+1. expressly accepting the applicable PTSIP License and Commercial Cooperation Duty;
+2. identifying the PTSIP version or immutable revision actually used;
+3. registering within 90 days of first Commercial Use; and
+4. continuing to satisfy attribution and cooperation duties.
+
+There is no default monetary license fee.
+
+See COMMERCIAL-USE.md for the current registration and reporting procedure.
+
+## Missed reports and correction
+
+The license is designed to prefer correction over punishment.
+
+Ordinary missed obligations have a 90-day cure period. The compliance periods are intended to encourage voluntary cooperation and reasonable correction, not to create traps for users acting in good faith. If the user cures the omission, ordinary suspended authorization can be automatically reinstated.
+
+Intentional attribution falsification, deliberately false reporting, concealment, or repeated attempts to evade reciprocity are treated more seriously.
+
+## Project decisions and shared improvement
+
+PTSIP supports project decisions; it does not replace the user's authority over the user's own project. Users decide how PTSIP guidance, classifications, validation results, and conformance results are applied in their own environments.
+
+A PTSIP conformance result means conformance to the applicable PTSIP rules. It is not intended as a general certification of every quality or property of the surrounding project.
+
+The cooperation model exists so that useful findings and improvements can return to the community. Reporting a finding does not make the reporter responsible for another user's independent application of PTSIP, and receiving a finding does not create a promise that the project will implement a particular correction within a particular period.
+
+## AI use
+
+PTSIP may be used for training, fine-tuning, evaluation, dataset construction, agent development, or compatibility testing.
+
+PTSIP attribution should appear in a reasonably discoverable model card, dataset record, training record, system documentation, technical documentation, research record, or equivalent place. The license does not require every model output to repeat the notice.
+
+Commercial AI use follows commercial reciprocity. Institutional noncommercial AI research follows research reciprocity.
+
+## Historical license versions
+
+The license attached to a particular PTSIP revision governs the permissions granted with that copy, subject to applicable law.
+
+Later PTSIP license versions do not silently rewrite earlier copies. A later PTSIP release may use a later license and may require acceptance of that later license for that later release.
+
+## Project files
+
+- [LICENSE.md](LICENSE.md) — controlling license text
+- [NOTICE.md](NOTICE.md) — standard attribution text
+- [LICENSE-GUIDE.md](LICENSE-GUIDE.md) — this plain-language guide
+- [COMMERCIAL-USE.md](COMMERCIAL-USE.md) — Standing Commercial Authorization, registration, and cooperation submission procedure

ptsip-0.3.8a2/License-Authority/LICENSE-HISTORY.md

@@ -0,0 +1,15 @@
+# PTSIP License History
+
+This file records licensing-policy provenance for the PTSIP project. It is informational unless LICENSE.md expressly incorporates a statement from this file.
+
+## PTSIP Community Reciprocity License 1.0
+
+- License identifier: `LicenseRef-PTSIP-Community-Reciprocity-1.0`
+- Effective Time: `2026-09-15T00:00:00Z`
+- Time basis: Coordinated Universal Time (UTC)
+- Status before Effective Time: published in advance for notice and preparation
+- Effect: prospective from the Effective Time; not retroactive
+
+The exact PTSIP material used by a registrant or reporting party must be identified by a PTSIP version or immutable revision. Where both a version and immutable revision are reasonably available, both should be recorded.
+
+Earlier PTSIP revisions may have been distributed under different license terms. This history does not revoke, rewrite, or invalidate rights that validly attached to an earlier copy under the license applicable to that copy.