Who can open it, and for how long.
A descriptor names a file. It does not open it. Opening needs the cell and a grant.
Three things must be present.
All three, or the file stays closed. Switch each one on and off.
A descriptor alone rebuilds nothing. It can travel in the open.
Wording for these three factors is under review.
A grant opens a window, then closes it.
Terms are enforced against the grant record Implexus holds, not trusted from the token.
- Access type
- View
- Timing
- From the start to the end of the grant
- Use count
- Three opens
Illustration. Access types and limits are set per grant.
Rebuilt only where the cell is present.
- The descriptor alone rebuilds nothing
- The cell is controlled by Implexus
- Decode runs before Regenerate, every time
What we claim, and what we do not
- No certification or penetration test is claimed
- No speed or strength figures
- No compliance claim
- Bit-exact regeneration, as shown in the demo
- Access checked at Decode, per grant
- Independent validation is in progress
Questions from security reviewers
Draft answers. To confirm with engineering and legal.
What happens if a descriptor is seen by someone else?
It names a file but rebuilds nothing on its own. Opening also needs the cell and a valid grant.
Who holds the cell?
Implexus. [Hosting and custody model: to confirm with engineering.]
Can a grant be withdrawn?
Yes. When a grant ends or is withdrawn, the file no longer opens for that party.
Is technical documentation available?
Yes, for security and engineering reviewers, on request. [Process: to confirm.]
Talk to us about security review.
Security and engineering reviewers: ask us about the technical documentation.