Skip to content

Commit 0aea9f1

Browse files
terceltercel
committed
chore: add project governance, legal, and contribution documentation
1 parent 5d1cb12 commit 0aea9f1

File tree

6 files changed

+438
-0
lines changed

6 files changed

+438
-0
lines changed

‎CODE_OF_CONDUCT.md‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
# Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a positive experience for everyone.
7+
8+
## Our Standards
9+
10+
Examples of behavior that contributes to a positive environment:
11+
12+
- Using welcoming and inclusive language
13+
- Being respectful of differing viewpoints and experiences
14+
- Gracefully accepting constructive criticism
15+
- Focusing on what is best for the community
16+
17+
Examples of unacceptable behavior:
18+
19+
- Personal attacks or derogatory comments
20+
- Public or private harassment
21+
- Publishing others' private information without permission
22+
23+
## Enforcement
24+
25+
Instances of unacceptable behavior may be reported to the project maintainers
26+
at: team@aiperceivable.org
27+
28+
All complaints will be reviewed and investigated and will result in a response
29+
that is deemed necessary and appropriate to the circumstances.
30+
31+
## Attribution
32+
33+
This Code of Conduct is adapted from the
34+
[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1.
35+
36+
For the full text, see:
37+
https://www.contributor-covenant.org/version/2/1/code_of_conduct/

‎CONTRIBUTING.md‎

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
# Contributing to apcore
2+
3+
Thank you for your interest in contributing to apcore!
4+
5+
## Ways to Contribute
6+
7+
- **Report bugs**: Open an issue describing the problem
8+
- **Propose features**: Open an issue with the `enhancement` label
9+
- **Submit code**: Fork, branch, and open a pull request
10+
- **Improve docs**: Fix typos, add examples, clarify language
11+
- **Review PRs**: Help review open pull requests
12+
13+
## Protocol Specification
14+
15+
The specification lives in [PROTOCOL_SPEC.md](PROTOCOL_SPEC.md). Changes to
16+
the spec require an issue discussing the change before a PR is opened.
17+
Spec changes must be reviewed by at least 2 maintainers.
18+
19+
## Language SDKs
20+
21+
Each SDK has its own repository with language-specific setup instructions:
22+
23+
| SDK | Repository | Setup |
24+
|-----|-----------|-------|
25+
| Python | [apcore-python](https://github.com/aiperceivable/apcore-python) | Python 3.11+, `pip install -e .` |
26+
| TypeScript | [apcore-typescript](https://github.com/aiperceivable/apcore-typescript) | Node 18+, `npm install` |
27+
| Rust | [apcore-rust](https://github.com/aiperceivable/apcore-rust) | Rust 1.75+, `cargo build` |
28+
29+
## Pull Request Process
30+
31+
1. Fork the repository and create a branch from `main`
32+
2. Make your changes with clear commit messages
33+
3. Add or update tests as appropriate
34+
4. Ensure all tests pass
35+
5. Open a PR with a description of the changes and why they are needed
36+
6. Wait for review — maintainers aim to respond within 7 days
37+
38+
## Developer Certificate of Origin (DCO)
39+
40+
All contributions must be signed off with DCO:
41+
42+
```
43+
git commit -s -m "Description of change"
44+
```
45+
46+
This certifies that you have the right to submit the contribution under
47+
the project's license. See [developercertificate.org](https://developercertificate.org/).
48+
49+
## Coding Guidelines
50+
51+
- Follow the existing code style in each repository
52+
- Write tests for new functionality
53+
- Keep PRs focused — one logical change per PR
54+
- Update documentation when changing user-facing behavior
55+
56+
## Cross-Language Consistency
57+
58+
When making changes that affect the protocol or module behavior, consider
59+
the impact across all three language implementations. Ideally, changes to
60+
the spec should be accompanied by PRs to all affected SDK repositories.
61+
62+
## Reporting Security Issues
63+
64+
Please see [SECURITY.md](SECURITY.md) for instructions on reporting
65+
security vulnerabilities. **Do not open public issues for security bugs.**
66+
67+
## License
68+
69+
By contributing, you agree that your contributions will be licensed under
70+
the [Apache License 2.0](LICENSE).

‎GOVERNANCE.md‎

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
# apcore Governance
2+
3+
## Overview
4+
5+
apcore is a specification and set of reference implementations for AI-perceivable
6+
module standards. This document describes the governance model for the apcore project
7+
and its sub-projects.
8+
9+
## Scope
10+
11+
This governance covers:
12+
- **apcore** — Protocol specification (PROTOCOL_SPEC.md)
13+
- **apcore-python**, **apcore-typescript**, **apcore-rust** — Language SDKs
14+
- **apcore-toolkit**, **apcore-toolkit-python/typescript/rust** — Schema transformation toolkit
15+
- **apcore-mcp**, **apcore-mcp-python/typescript/rust** — MCP protocol bridge
16+
- **apcore-a2a**, **apcore-a2a-python/typescript** — A2A protocol bridge
17+
- **apcore-cli**, **apcore-cli-python/typescript/rust** — CLI adapter
18+
19+
## Maintainers
20+
21+
The project is governed by its maintainers as listed in [MAINTAINERS.md](MAINTAINERS.md).
22+
23+
Maintainers have commit access and are responsible for:
24+
- Reviewing and merging contributions
25+
- Maintaining the specification and reference implementations
26+
- Setting technical direction
27+
- Ensuring cross-language consistency
28+
29+
## Decision Making
30+
31+
- **Consensus-based**: Decisions are made by consensus among maintainers
32+
- **Lazy consensus**: Proposals are accepted if no maintainer objects within 7 days
33+
- **Voting**: If consensus cannot be reached, a simple majority vote among maintainers decides
34+
- **Spec changes**: Changes to PROTOCOL_SPEC.md require review and approval by at least 2 maintainers (or all maintainers if fewer than 3 exist)
35+
36+
## Becoming a Maintainer
37+
38+
New maintainers are nominated by existing maintainers based on:
39+
- Sustained, quality contributions over 3+ months
40+
- Demonstrated understanding of the project's goals and architecture
41+
- Willingness to commit time to reviews and project stewardship
42+
43+
Nomination requires approval from a majority of current maintainers.
44+
45+
## Contributor Roles
46+
47+
| Role | Description | Requirements |
48+
|------|-------------|--------------|
49+
| **Contributor** | Anyone who submits a PR or issue | Sign DCO |
50+
| **Reviewer** | Trusted to review PRs in a specific area | Consistent quality contributions |
51+
| **Maintainer** | Full commit access, sets direction | Nominated + majority approval |
52+
53+
## Sub-projects
54+
55+
Each language SDK and bridge is a sub-project under this governance. Sub-projects
56+
may have additional maintainers specific to that language or domain, but all
57+
sub-projects follow this governance document.
58+
59+
## Code of Conduct
60+
61+
All participants must follow the [Code of Conduct](CODE_OF_CONDUCT.md).
62+
63+
## Changes to Governance
64+
65+
Changes to this document require approval from 2/3 of current maintainers.

‎LICENSE‎

Lines changed: 190 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,190 @@
1+
Apache License
2+
Version 2.0, January 2004
3+
http://www.apache.org/licenses/
4+
5+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6+
7+
1. Definitions.
8+
9+
"License" shall mean the terms and conditions for use, reproduction,
10+
and distribution as defined by Sections 1 through 9 of this document.
11+
12+
"Licensor" shall mean the copyright owner or entity authorized by
13+
the copyright owner that is granting the License.
14+
15+
"Legal Entity" shall mean the union of the acting entity and all
16+
other entities that control, are controlled by, or are under common
17+
control with that entity. For the purposes of this definition,
18+
"control" means (i) the power, direct or indirect, to cause the
19+
direction or management of such entity, whether by contract or
20+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
21+
outstanding shares, or (iii) beneficial ownership of such entity.
22+
23+
"You" (or "Your") shall mean an individual or Legal Entity
24+
exercising permissions granted by this License.
25+
26+
"Source" form shall mean the preferred form for making modifications,
27+
including but not limited to software source code, documentation
28+
source, and configuration files.
29+
30+
"Object" form shall mean any form resulting from mechanical
31+
transformation or translation of a Source form, including but
32+
not limited to compiled object code, generated documentation,
33+
and conversions to other media types.
34+
35+
"Work" shall mean the work of authorship, whether in Source or
36+
Object form, made available under the License, as indicated by a
37+
copyright notice that is included in or attached to the work
38+
(an example is provided in the Appendix below).
39+
40+
"Derivative Works" shall mean any work, whether in Source or Object
41+
form, that is based on (or derived from) the Work and for which the
42+
editorial revisions, annotations, elaborations, or other modifications
43+
represent, as a whole, an original work of authorship. For the purposes
44+
of this License, Derivative Works shall not include works that remain
45+
separable from, or merely link (or bind by name) to the interfaces of,
46+
the Work and Derivative Works thereof.
47+
48+
"Contribution" shall mean any work of authorship, including
49+
the original version of the Work and any modifications or additions
50+
to that Work or Derivative Works thereof, that is intentionally
51+
submitted to the Licensor for inclusion in the Work by the copyright owner
52+
or by an individual or Legal Entity authorized to submit on behalf of
53+
the copyright owner. For the purposes of this definition, "submitted"
54+
means any form of electronic, verbal, or written communication sent
55+
to the Licensor or its representatives, including but not limited to
56+
communication on electronic mailing lists, source code control systems,
57+
and issue tracking systems that are managed by, or on behalf of, the
58+
Licensor for the purpose of discussing and improving the Work, but
59+
excluding communication that is conspicuously marked or otherwise
60+
designated in writing by the copyright owner as "Not a Contribution."
61+
62+
"Contributor" shall mean Licensor and any individual or Legal Entity
63+
on behalf of whom a Contribution has been received by the Licensor and
64+
subsequently incorporated within the Work.
65+
66+
2. Grant of Copyright License. Subject to the terms and conditions of
67+
this License, each Contributor hereby grants to You a perpetual,
68+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69+
copyright license to reproduce, prepare Derivative Works of,
70+
publicly display, publicly perform, sublicense, and distribute the
71+
Work and such Derivative Works in Source or Object form.
72+
73+
3. Grant of Patent License. Subject to the terms and conditions of
74+
this License, each Contributor hereby grants to You a perpetual,
75+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76+
(except as stated in this section) patent license to make, have made,
77+
use, offer to sell, sell, import, and otherwise transfer the Work,
78+
where such license applies only to those patent claims licensable
79+
by such Contributor that are necessarily infringed by their
80+
Contribution(s) alone or by combination of their Contribution(s)
81+
with the Work to which such Contribution(s) was submitted. If You
82+
institute patent litigation against any entity (including a
83+
cross-claim or counterclaim in a lawsuit) alleging that the Work
84+
or a Contribution incorporated within the Work constitutes direct
85+
or contributory patent infringement, then any patent licenses
86+
granted to You under this License for that Work shall terminate
87+
as of the date such litigation is filed.
88+
89+
4. Redistribution. You may reproduce and distribute copies of the
90+
Work or Derivative Works thereof in any medium, with or without
91+
modifications, and in Source or Object form, provided that You
92+
meet the following conditions:
93+
94+
(a) You must give any other recipients of the Work or
95+
Derivative Works a copy of this License; and
96+
97+
(b) You must cause any modified files to carry prominent notices
98+
stating that You changed the files; and
99+
100+
(c) You must retain, in the Source form of any Derivative Works
101+
that You distribute, all copyright, patent, trademark, and
102+
attribution notices from the Source form of the Work,
103+
excluding those notices that do not pertain to any part of
104+
the Derivative Works; and
105+
106+
(d) If the Work includes a "NOTICE" text file as part of its
107+
distribution, then any Derivative Works that You distribute must
108+
include a readable copy of the attribution notices contained
109+
within such NOTICE file, excluding any notices that do not
110+
pertain to any part of the Derivative Works, in at least one
111+
of the following places: within a NOTICE text file distributed
112+
as part of the Derivative Works; within the Source form or
113+
documentation, if provided along with the Derivative Works; or,
114+
within a display generated by the Derivative Works, if and
115+
wherever such third-party notices normally appear. The contents
116+
of the NOTICE file are for informational purposes only and
117+
do not modify the License. You may add Your own attribution
118+
notices within Derivative Works that You distribute, alongside
119+
or as an addendum to the NOTICE text from the Work, provided
120+
that such additional attribution notices cannot be construed
121+
as modifying the License.
122+
123+
You may add Your own copyright statement to Your modifications and
124+
may provide additional or different license terms and conditions
125+
for use, reproduction, or distribution of Your modifications, or
126+
for any such Derivative Works as a whole, provided Your use,
127+
reproduction, and distribution of the Work otherwise complies with
128+
the conditions stated in this License.
129+
130+
5. Submission of Contributions. Unless You explicitly state otherwise,
131+
any Contribution intentionally submitted for inclusion in the Work
132+
by You to the Licensor shall be under the terms and conditions of
133+
this License, without any additional terms or conditions.
134+
Notwithstanding the above, nothing herein shall supersede or modify
135+
the terms of any separate license agreement you may have executed
136+
with Licensor regarding such Contributions.
137+
138+
6. Trademarks. This License does not grant permission to use the trade
139+
names, trademarks, service marks, or product names of the Licensor,
140+
except as required for reasonable and customary use in describing the
141+
origin of the Work and reproducing the content of the NOTICE file.
142+
143+
7. Disclaimer of Warranty. Unless required by applicable law or
144+
agreed to in writing, Licensor provides the Work (and each
145+
Contributor provides its Contributions) on an "AS IS" BASIS,
146+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147+
implied, including, without limitation, any warranties or conditions
148+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149+
PARTICULAR PURPOSE. You are solely responsible for determining the
150+
appropriateness of using or redistributing the Work and assume any
151+
risks associated with Your exercise of permissions under this License.
152+
153+
8. Limitation of Liability. In no event and under no legal theory,
154+
whether in tort (including negligence), contract, or otherwise,
155+
unless required by applicable law (such as deliberate and grossly
156+
negligent acts) or agreed to in writing, shall any Contributor be
157+
liable to You for damages, including any direct, indirect, special,
158+
incidental, or consequential damages of any character arising as a
159+
result of this License or out of the use or inability to use the
160+
Work (including but not limited to damages for loss of goodwill,
161+
work stoppage, computer failure or malfunction, or any and all
162+
other commercial damages or losses), even if such Contributor
163+
has been advised of the possibility of such damages.
164+
165+
9. Accepting Warranty or Additional Liability. While redistributing
166+
the Work or Derivative Works thereof, You may choose to offer,
167+
and charge a fee for, acceptance of support, warranty, indemnity,
168+
or other liability obligations and/or rights consistent with this
169+
License. However, in accepting such obligations, You may act only
170+
on Your own behalf and on Your sole responsibility, not on behalf
171+
of any other Contributor, and only if You agree to indemnify,
172+
defend, and hold each Contributor harmless for any liability
173+
incurred by, or claims asserted against, such Contributor by reason
174+
of your accepting any such warranty or additional liability.
175+
176+
END OF TERMS AND CONDITIONS
177+
178+
Copyright 2026 AI Perceivable Contributors
179+
180+
Licensed under the Apache License, Version 2.0 (the "License");
181+
you may not use this file except in compliance with the License.
182+
You may obtain a copy of the License at
183+
184+
http://www.apache.org/licenses/LICENSE-2.0
185+
186+
Unless required by applicable law or agreed to in writing, software
187+
distributed under the License is distributed on an "AS IS" BASIS,
188+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
189+
See the License for the specific language governing permissions and
190+
limitations under the License.

‎MAINTAINERS.md‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
# Maintainers
2+
3+
## Current Maintainers
4+
5+
| Name | GitHub | Affiliation | Scope |
6+
|------|--------|-------------|-------|
7+
| Tercel Yi | [@tercel](https://github.com/tercel) | AI Perceivable | All |
8+
9+
## Emeritus Maintainers
10+
11+
(None yet)
12+
13+
## Sub-project Maintainers
14+
15+
As the community grows, sub-project maintainers for specific language SDKs
16+
and bridges will be listed here.
17+
18+
| Sub-project | Maintainer | GitHub |
19+
|-------------|-----------|--------|
20+
| apcore-python | Tercel Yi | [@tercel](https://github.com/tercel) |
21+
| apcore-typescript | Tercel Yi | [@tercel](https://github.com/tercel) |
22+
| apcore-rust | Tercel Yi | [@tercel](https://github.com/tercel) |
23+
| apcore-toolkit-* | Tercel Yi | [@tercel](https://github.com/tercel) |
24+
| apcore-mcp-* | Tercel Yi | [@tercel](https://github.com/tercel) |
25+
| apcore-a2a-* | Tercel Yi | [@tercel](https://github.com/tercel) |
26+
| apcore-cli-* | Tercel Yi | [@tercel](https://github.com/tercel) |

0 commit comments

Comments
 (0)