Skip to content

[API Proposal] TrustWorthiness Intent API #293 #294

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
panos-ece wants to merge 6 commits into
base: main
Choose a base branch
from
Open

[API Proposal] TrustWorthiness Intent API #293 #294

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
377c656
[API Proposal] TrustWorthiness Intent API #293
panos-ece Dec 22, 2025
902cb40
[API Proposal] TrustWorthiness Intent API #293 #294
panos-ece Dec 23, 2025
a4ddc07
Update the proposal template and provide pdf for the presentation
panos-ece Jan 21, 2026
1eda21f
Small update on the presentation
panos-ece Jan 22, 2026
a7e1d88
Fix the name of the API proposal
panos-ece Jan 28, 2026
8484943
Enhance API proposal with APs
panos-ece Feb 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
53 changes: 53 additions & 0 deletions documentation/API proposals/TrustWorthiness_Intent_API_proposal.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
# API Proposal Template

This template captures all the information that a partner should fill out when proposing a new API (or API family) to CAMARA.

### API family name

TrustWorthiness Intent.

### API family owner

National Centre for Scientific Research Demokritos (NCSRD)
and Infolysis P.C.

### API summary

A Trustworthiness Intent API enabling developers and applications to request and
monitor trust guarantees (security, privacy, reliability, resilience,safety) as
high-level intents without specifying low-level configurations.

### Technical viability

No network/cloud capabilities required. The API's bussiness logic is supported through an open-source
AI-native trust orchestrator acts as the backend to produce trust scores to feed them in the correspondent network.

### Commercial viability

An open-source implementation is used called Cognitive Coordinator (CoCo), that is, an AI-native trust orchestrator.
It interprets user trust intents expressed in natural language and translates them into actionable system configurations,
dynamically computing a Level of Trustworthiness (LoT) that aligns with both semantic intent and real-world resource constraints.

This is part of the SAFE-6G European Horizon project. (https://safe-6g.eu/)

### YAML code available?

YES

### Validated in lab/productive environments?

YES, lab network.

### Validated with real customers?

NO

### Validated with operators?

NO

### Supporters in API Backlog Working Group
Infolysis P.C.

List of supporters.
Copy link
Contributor

@albertoramosmonagas albertoramosmonagas Dec 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @panos-ece, from the proposal, I understand that Infosys would have to be at this point? Also, for readability, could you remove what is part of the template and leave only the useful information? That is, from here:

### API family name

Name of the API or API family.

CAMARA TrustWorthiness INTENT API.

We would leave only:

### API family name

CAMARA TrustWorthiness INTENT API.

This makes it easier to review. If you could apply this to the rest of the document.

Copy link
Author

@panos-ece panos-ece Dec 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @albertoramosmonagas , I have updated the template after your comments. One question about the infolysis P.C. part. Due to the common proposal part, should they commit as well, or is it just fine to somehow list the author in the PR description?

Copy link
Contributor

@albertoramosmonagas albertoramosmonagas Dec 23, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be sufficient to put them on the list of supporters. I understand that if this API moves on to repository creation, infolysis would become a maintainer or code owner?

Copy link
Author

@panos-ece panos-ece Jan 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @albertoramosmonagas, I have updated the proposal template with the infolysis as well in the supporters section.

_NOTE: That shall be added by the Working Group. Supporting an API proposal means that the supporting company must provide at least 1 (one) Maintainer at the time of the Sub Project creation._
Binary file added ...portingDocuments/trustworthiness_intent_api/CAMARA_API_PROPOSAL_TrustWorthinessIntent.pdf
View file
Open in desktop
Binary file not shown.
Loading