NOISSUE added some files for needed

Signed-off-by: Mehmet Samet Duman <yongdohyun@projecttick.org>

4 files changed, 344 insertions, 0 deletions

diff --git a/CODEOWNERS b/CODEOWNERS
new file mode 100644
index 0000000000..5ebe1d65f7
--- /dev/null
+++ b/CODEOWNERS
@@ -0,0 +1 @@
+* @YongDo-Hyun
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000000..56e899ac8b
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,169 @@
+# Contributing to Project Tick
+
+## Restrictions on Generative AI Usage (AI Policy)
+> [!NOTE]
+> The following is adapted from [matplotlib's contributing guide](https://matplotlib.org/devdocs/devel/contribute.html#generative-ai) and the [Linux Kernel policy guide](https://www.kernel.org/doc./html/next/process/coding-assistants.html)
+
+We expect authentic engagement in our community.
+
+- Do not post output from Large Language Models or similar generative AI as comments on Github or our discord server, as such comments tend to be formulaic and low-quality content.
+- If you use generative AI tools as an aid in developing code or documentation changes, ensure that you fully understand the proposed changes and can explain why they are the correct approach.
+
+Make sure you have added value based on your personal competency to your contributions. 
+Just taking some input, feeding it to an AI and posting the result is not of value to the project. 
+To preserve precious core developer capacity, we reserve the right to rigorously reject seemingly AI generated low-value contributions.
+
+### Signed-off-by and Developer Certificate of Origin 
+
+AI agents MUST NOT add Signed-off-by tags. Only humans can legally certify the Developer Certificate of Origin (DCO). The human submitter is responsible for:
+
+  - Reviewing all AI-generated code
+  - Ensuring compliance with licensing requirements
+  - Adding their own Signed-off-by tag to certify the DCO
+  - Taking full responsibility for the contribution
+  
+See [Signing your work](#signing-your-work) for more information.
+
+
+### Attribution
+
+When AI tools contribute to development, proper attribution helps track the evolving role of AI in the development process. Contributions should include an Assisted-by tag in the commit message with the following format:
+
+```
+Assisted-by: AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]
+```
+
+Where:
+
+  - `AGENT_NAME` is the name of the AI tool or framework
+  - `MODEL_VERSION` is the specific model version used
+  - `[TOOL1] [TOOL2]` are optional specialized analysis tools used (e.g., coccinelle, sparse, smatch, clang-tidy)
+
+Basic development tools (git, gcc, make, editors) should not be listed.
+
+Example:
+
+```
+Assisted-by: Claude:claude-3-opus coccinelle sparse
+```
+
+## Contributor License Agreement (CLA)
+
+By submitting a contribution to this repository, you agree that your
+contribution is made under the terms of the **Project Tick Contributor
+License Agreement (CLA)**.
+
+The CLA ensures that:
+
+- you have the legal right to submit the contribution,
+- the contribution does not knowingly infringe third-party rights,
+- Project Tick may distribute the contribution under the applicable
+  Project Tick license(s) governing the component,
+- long-term governance and license consistency across the Project Tick
+  ecosystem can be maintained.
+
+The CLA applies to all intentional contributions, including but not
+limited to source code, documentation, tests, data, media assets, and
+configuration files.
+
+The full text of the current CLA is available at:
+
+- <https://projecttick.org/licenses/PT-CLA-2.0.txt>
+
+If you do not agree to the CLA, please do not submit contributions.
+
+---
+
+## Quick Start
+
+Please read the [handbook](docs/handbook/) for the section you are interested in. Example: ProjT Launcher
+
+---
+
+## Commit Messages
+
+```text
+subproject(component): short description
+
+Optional explanation of what and why.
+```
+
+Examples:
+
+```text
+projtlauncher(fix): fix crash on startup with invalid config
+```
+
+---
+
+## DCO Sign-off
+
+Every commit must include a sign-off line and all files to commit:
+
+```sh
+git commit -s -a
+```
+
+This adds:
+
+```text
+Signed-off-by: Your Name <your.email@example.com>
+```
+
+The bot enforces DCO compliance and labels PRs missing sign-off.
+
+---
+
+## Merge Request Process
+
+### Before Submitting
+
+- Run clang-format on changed files
+- Ensure code compiles without warnings
+- Add tests for new functionality
+- Sign off all commits
+- Update documentation if needed
+
+### PR Requirements
+
+- Clear description of what and why
+- Reference related issues
+- Pass all CI checks
+- One logical change per PR
+- **Do not mix**: refactors, features, and third-party updates must be in separate PRs
+- Third-party library updates require standalone PRs with documented rationale
+
+### Review Process
+
+1. Automated CI runs tests and linting
+2. Maintainer reviews code
+3. Address feedback
+4. Merge when approved
+
+---
+
+## Documentation
+
+See `docs/` for detailed documentation:
+
+- [docs/contributing/](docs/contributing/) - Contribution guides
+- [docs/handbook/](docs/handbook/) - Developer handbook
+- [docs/](docs/) - General documentation
+
+---
+
+## Contact
+
+- Issues: [GitHub Issues](https://github.com/Project-Tick/Project-Tick/issues)
+- Email: [projecttick@projecttick.org](mailto:projecttick@projecttick.org)
+
+---
+
+## License
+
+By contributing, you agree to license your work under the project's licenses.
+See [LICENSES/](LICENSES/) folder.
+
+## Code of Conduct
+
+See [CODE_OF_CONDUCT](CODE_OF_CONDUCT).
diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 0000000000..1a3ce799f0
--- /dev/null
+++ b/SECURITY.md
@@ -0,0 +1,16 @@
+# Security Policy
+
+## How to report
+
+If you discover a security vulnerability, please report it via email:
+
+- [`projecttick@projecttick.org`](mailto:projecttick@projecttick.org)
+
+## What to include
+
+When submitting a report, please include:
+
+- Steps to reproduce the issue
+- Expected and actual behavior
+- Affected versions
+- Logs or crash reports if available
diff --git a/TRADEMARK.md b/TRADEMARK.md
new file mode 100644
index 0000000000..2e5cd8c22e
--- /dev/null
+++ b/TRADEMARK.md
@@ -0,0 +1,158 @@
+## TRADEMARK NOTICE
+
+### Project Tick™ Trademark and Brand Policy
+
+#### 1. Ownership of the Marks
+
+Project Tick™, the Project Tick name, the Project Tick logo, and all related branding elements (collectively, the “Marks”) are trademarks of **Mehmet Samet Duman**.
+
+All rights in the Marks are reserved.
+
+This Trademark Policy governs use of the Marks independently of any open source license applicable to source code, documentation, or other materials.
+
+---
+
+#### 2. Relationship to Open Source Licenses
+
+Each repository under the Project Tick namespace is licensed under its respective open source license (e.g., MIT, BSD, Apache-2.0, GPL, MS-PL, etc.).
+
+These licenses govern the use, modification, and redistribution of source code only.
+
+Open source licenses do **not** grant:
+
+* Rights to use the Project Tick name
+* Rights to use the Project Tick logo
+* Rights to use Project Tick branding or trade dress
+* Rights to imply affiliation, endorsement, sponsorship, or official status
+
+Trademark rights are separate from copyright licenses.
+
+---
+
+#### 3. Permitted Uses
+
+The following uses are generally permitted without prior written permission:
+
+1. Factual references (e.g., “compatible with Project Tick”).
+2. Accurate description of unmodified official releases.
+3. Non-commercial commentary, research, educational, or journalistic references.
+
+Permitted use must not:
+
+* Create confusion regarding origin
+* Suggest sponsorship, approval, or endorsement
+* Present modified versions as official releases
+
+---
+
+#### 4. Modified and Redistributed Versions
+
+Open source licenses permit modification and redistribution of source code.
+
+However:
+
+* Modified versions must not use the Project Tick name or logo in a way that implies official status.
+* Forks must use distinct branding.
+* Derivative works must clearly indicate that they are modified versions.
+* Use of phrases such as “Official,” “Certified,” or similar terminology is prohibited without authorization.
+
+Permissible example:
+
+> “Based on Project Tick”
+
+Impermissible example:
+
+> “Official Project Tick Build”
+
+Unless explicitly authorized.
+
+---
+
+#### 5. Commercial Use and SaaS Deployments
+
+The Marks may not be used:
+
+* As part of a product name
+* As part of a company name
+* As part of a commercial SaaS service name
+* As part of a registered domain name
+* In paid advertising or promotional materials
+
+Without prior written permission.
+
+Operating a commercial service using Project Tick source code does not grant the right to represent that service as an official Project Tick service.
+
+Only services directly operated by Mehmet Samet Duman under the Project Tick identity may use the Marks in a commercial context.
+
+---
+
+#### 6. Official Releases
+
+An “Official Project Tick Release” is a version that:
+
+* Is built and distributed by the Project Tick maintainers
+* Is published through official communication channels
+* Is identified by official release tags or signatures
+
+Modified builds, even if compliant with the applicable open source license, must not be presented as official releases.
+
+---
+
+#### 7. Logo Usage
+
+The Project Tick logo is protected by copyright and trademark law.
+
+If licensed under a Creative Commons license (e.g., CC BY-NC-ND), such license applies only within its stated scope and does not waive trademark protections.
+
+The logo may not be:
+
+* Modified
+* Recolored
+* Combined with other marks
+* Used for commercial services
+* Embedded in derivative branding
+
+Without written authorization.
+
+---
+
+#### 8. Domain Names and Corporate Identifiers
+
+The Marks may not be used:
+
+* In domain names
+* In social media handles
+* In corporate names
+* In registered business identifiers
+
+Without explicit written permission.
+
+---
+
+#### 9. Prohibited Uses
+
+The following uses are strictly prohibited:
+
+* Implying endorsement or affiliation
+* Misrepresenting unofficial builds as official
+* Using the Marks in a misleading or deceptive manner
+* Using the Marks in ways that damage reputation or goodwill
+* Registering confusingly similar names
+
+---
+
+#### 10. Reservation of Rights
+
+All rights not expressly granted in this policy are reserved.
+
+Failure to enforce any provision of this policy shall not constitute a waiver of any rights.
+
+Project Tick reserves the right to update this policy at any time.
+
+---
+
+#### 11. Contact
+
+For permission requests or questions regarding trademark use:
+
+[yongdohyun@projecttick.org](mailto:yongdohyun@projecttick.org)